From Fedora Project Wiki

m (add category)
(polish instructions)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description= Install Fedora CoreOS in a libvirt. For the sake of the testing the freshly-oven-baked changes, we would be using the <code>next</code> image.  
+
|description=Install Fedora CoreOS as a virtual machine using the <code>next</code> image.
 
|setup=
 
|setup=
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS <b>next</b> image for QEMU]
+
# Download and verify the latest [https://getfedora.org/coreos/download?tab=metal_virtualized&stream=next FCOS '''next''' image for QEMU]
 +
# 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=
# Prepare an Ignition file to configure your FCOS instance. Read [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_provisioning_philosophy Provisioning Philosophy]
+
# [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ Create an Ignition file]. You can use the simplest example available.
# [https://docs.fedoraproject.org/en-US/fedora-coreos/producing-ign/ Produce the ignition file].
 
 
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_launching_with_qemu_or_libvirt Launching with QEMU or libvirt] documentation to start up a virtual machine.
 
# Follow [https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/#_launching_with_qemu_or_libvirt Launching with QEMU or libvirt] documentation to start up a virtual machine.
 +
# Log in to your new FCOS system (with the username and password configured in your Ignition file) using the serial console (you're automatically connected to it when you run the installation through `qemu-kvm` or `virt-install`).
 +
# 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 in a virtual 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 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.
# The virtual machine once destroyed, should deallocate all resources.
 
 
 
|optional=If you see some issues, investigate the logs in journal, make sure the services are running.
 
# To be added
 
 
}}
 
}}
  
 
[[Category:CoreOS Test Cases]]
 
[[Category:CoreOS Test Cases]]

Revision as of 11:18, 2 June 2020

Description

Install Fedora CoreOS as a virtual machine using the next image.

Setup

  1. Download and verify the latest FCOS next image for QEMU
  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 Launching with QEMU or libvirt documentation to start up a virtual machine.
  3. Log in to your new FCOS system (with the username and password configured in your Ignition file) using the serial console (you're automatically connected to it when you run the installation through qemu-kvm or virt-install).
  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 in a virtual 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.