From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 25: | Line 25: | ||
State: idle | State: idle | ||
Deployments: | Deployments: | ||
* ostree://fedora:fedora/x86_64/coreos/next | |||
Version: 33.20201104.1.0 | Version: 33.20201104.1.0 | ||
Revision as of 11:20, 6 November 2020
Description
This tests whether an existing Fedora CoreOS instance running on the stable stream can switch to the next stream.
Setup
- Have access to a (or install a new) FCOS instance running the stable stream.
How to test
- Verify that your FCOS system is running on stable:
$ sudo rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: * ostree://fedora:fedora/x86_64/coreos/stable Version: 32.20201018.3.0 (2020-11-02T20:54:53Z)
The black circle * shows the currently booted tree (if you see multiple deployments available). The current tree should show
fedora/x86_64/coreos/stable
. The version may differ from the above output. - Follow the Update Streams documentation to switch your system to the
next
stream.- A package difference should be displayed during the switch operation for you to review.
- Reboot
- Verify that your system is now running on the next stream:
$ sudo rpm-ostree status State: idle Deployments: * ostree://fedora:fedora/x86_64/coreos/next Version: 33.20201104.1.0
The current tree should show
fedora/x86_64/coreos/next
. The version may differ from the above output.
Expected Results
- The system successfully reboots and runs on the next stream.
- The system is functional (you can connect the same way as before, your services are running as before).
- The linked documentation is clear, all steps are understandable, and nothing important is missing from it.
Optional
- Before switching to the next stream, try for example creating containers or configuring a service and verify that the changes are successfully carried over after switching.
- After switching to the next stream, attempt both a temporary and a permanent manual rollback. After each rollback, verify that your system booted with the correct filesystem tree using
sudo rpm-ostree status
.