From Fedora Project Wiki

m (add category)
(polish instructions)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description= Install Fedora CoreOS on bare metal machine. For the sake of the testing the freshly-oven-baked changes, we would be using the <code>next</code> image.  
+
|description=Install Fedora CoreOS on bare metal machine using the `next` image.  
 
|setup=
 
|setup=
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS <b>next</b> image for bare metal]. Choose your preferred installation source (ISO for an optical or USB drive, PXE for a network install or Raw for a direct disk copy to a hard drive.)
+
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS '''next''' image for bare metal machines]. Choose your preferred installation source (''ISO'' for an optical or USB drive, ''PXE'' for a network install or ''Raw'' for a direct disk copy to a hard drive.)
 +
# Familiarize yourself with FCOS [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_provisioning_philosophy provisioning philosophy], i.e. the role of a an Ignition file during system installation.
  
 
|actions=
 
|actions=
 +
# [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ Create an Ignition file]. You can use the simplest example available.
 
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/ Installing CoreOS on Bare Metal] documentation to install FCOS to a bare metal machine.
 
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/ Installing CoreOS on Bare Metal] documentation to install FCOS to a bare metal machine.
#* '''FIXME:''' Raw installation instructions are not available in the linked documentation. Furthermore, it's not clear what "Raw (4k Native)" download option exactly means.
+
# Log in to your new FCOS system (with the username and password configured in your Ignition file) using the text console.
 +
# See the IP address printed at the login prompt (alternatively, you can also find it in the `ip address` command output).
 +
# SSH into the machine using `ssh username@ipaddress` (replace ''username'' and ''ipaddress'' with actual values).
  
 
|results=
 
|results=
The following must be true to consider this a successful test run:
+
# The system runs on a bare metal machine according to the instructions.
# Confirm that you can SSH successfully into the machine according to the instructions (and the contents of your Ignition file).
+
# You can connect through serial console and SSH.
# Verify that the linked documentation works without a hitch and all steps are understandable.
+
# The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
 
 
|optional=If you see some issues, investigate the logs in journal, make sure the services are running.
 
 
}}
 
}}
  
 
[[Category:CoreOS Test Cases]]
 
[[Category:CoreOS Test Cases]]

Revision as of 11:43, 2 June 2020

Description

Install Fedora CoreOS on bare metal machine using the next image.

Setup

  1. Download and verify the latest FCOS next image for bare metal machines. Choose your preferred installation source (ISO for an optical or USB drive, PXE for a network install or Raw for a direct disk copy to a hard drive.)
  2. Familiarize yourself with FCOS provisioning philosophy, i.e. the role of a an Ignition file during system installation.

How to test

  1. Create an Ignition file. You can use the simplest example available.
  2. Follow Installing CoreOS on Bare Metal documentation to install FCOS to a bare metal machine.
  3. Log in to your new FCOS system (with the username and password configured in your Ignition file) using the text console.
  4. See the IP address printed at the login prompt (alternatively, you can also find it in the ip address command output).
  5. SSH into the machine using ssh username@ipaddress (replace username and ipaddress with actual values).

Expected Results

  1. The system runs on a bare metal machine according to the instructions.
  2. You can connect through serial console and SSH.
  3. The linked documentation is clear, all steps are understandable, and nothing important is missing from it.