From Fedora Project Wiki

m (Dustymabe moved page QA:Testcase debugging toolbox to QA:Testcase CoreOS debugging toolbox: Add CoreOS to make page title more conformant)
No edit summary
Line 3: Line 3:
|setup=
|setup=
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS <b>next</b> image] (pick the right image for your environment).
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS <b>next</b> image] (pick the right image for your environment).
# Toolbox can be installed on Fedora with the following commands [https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/]  
# Toolbox is preinstalled on Fedora [https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/]  
    * Fedora Workstation (or any package-based version of Fedora) - '''$ sudo dnf install toolbox''' 
  ''Note:'' Use the latest image '''''registry.fedoraproject.org/fedora-toolbox:35'''''  
    * Fedora Silverblue - Toolbox is preinstalled on Fedora Silverblue 30 or newer.
      Older versions can use the command '''$ rpm-ostree install toolbox'''
''Note:'' Use the latest image '''''registry.fedoraproject.org/fedora-toolbox:35'''''  




Line 13: Line 10:
# [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ Create an Ignition file].  
# [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ Create an Ignition file].  
# Launch your Fedora CoreOS system using this Ignition file. See [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_quickstart the Quickstart] and the provisioning docs for a guide how to launch FCOS in most environments (bare metal, virtual, cloud, etc).
# Launch your Fedora CoreOS system using this Ignition file. See [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_quickstart the Quickstart] and the provisioning docs for a guide how to launch FCOS in most environments (bare metal, virtual, cloud, etc).
# [https://docs.fedoraproject.org/en-US/fedora-coreos/debugging-with-toolbox/ Debugging with Toolbox]
# Follow the documentation for [https://docs.fedoraproject.org/en-US/fedora-coreos/debugging-with-toolbox/ Debugging with Toolbox] and execute some debugging commands.


|results=
|results=
# You can SSH successfully into your FCOS system.
# You can SSH successfully into your FCOS system.
# Once inside the toolbox, you can access common command line tools, and install new ones using a package manager (e.g., DNF on Fedora).
# Once inside the toolbox, you can access common command line tools, and install new ones using a package manager (e.g., DNF on Fedora).
# Once done with your container, you can exit the container and then remove it from the host with the command. '''toolbox rm --force fedora-toolbox-35'''
# Once done with your container, you can exit the container and then remove it from the host.
# The linked documentation makes sense, nothing is obviously missing, and the instructions are clear.
# The linked documentation makes sense, nothing is obviously missing, and the instructions are clear.
}}
}}


[[Category:CoreOS Test Cases]]
[[Category:CoreOS Test Cases]]

Revision as of 18:43, 6 April 2022

Description

Provision Fedora CoreOS and configure fedora-toolbox:35 .

Setup

  1. Download and verify the latest FCOS next image (pick the right image for your environment).
  2. Toolbox is preinstalled on Fedora [1]
 Note: Use the latest image registry.fedoraproject.org/fedora-toolbox:35 

How to test

  1. Create an Ignition file.
  2. Launch your Fedora CoreOS system using this Ignition file. See the Quickstart and the provisioning docs for a guide how to launch FCOS in most environments (bare metal, virtual, cloud, etc).
  3. Follow the documentation for Debugging with Toolbox and execute some debugging commands.

Expected Results

  1. You can SSH successfully into your FCOS system.
  2. Once inside the toolbox, you can access common command line tools, and install new ones using a package manager (e.g., DNF on Fedora).
  3. Once done with your container, you can exit the container and then remove it from the host.
  4. The linked documentation makes sense, nothing is obviously missing, and the instructions are clear.