|Fedora Test Days|
What to test?
Today's instalment of Fedora Test Day will focus on FedUp, the Fedora system upgrade tool.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Will Woods (wwoods)
- Quality Assurance - Adam Williamson (adamw), Petr Schindl (pschindl)
Prerequisite for Test Day
A system with Fedora 20 or 21 you can use for test purposes (i.e. you don't mind if it all goes wrong and you lose the system)! Testing with a virtual machine will be useful for many cases, and will let you run multiple tests easily.
How to test?
The test procedure is simply to take a Fedora 20 or Fedora 21 installation and upgrade it to Fedora 22. To ensure you get the latest fedup for testing, run one of these two commands (depending on whether it's already installed):
yum --enablerepo=updates-testing install fedup yum --enablerepo=updates-testing update fedup
To upgrade, run (F21):
fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os
fedup --network 22 --product (product) --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os
where (arch) is the appropriate architecture (armhfp, x86_64, or i386) and (product) is the most appropriate 'product' for the install - see this note.
The idea is to test upgrades from as many different starting situations as possible - particularly with different package sets, languages, keyboard layouts, and storage configurations.
If the upgrade completes successfully, test the upgraded system to ensure it works correctly.
If any of your upgrades fails (or leads to a broken system), report a bug to Bugzilla. The correct component will depend on the exact nature of the bug - ask in IRC if you're unsure. If you can't find out what component to file against, file the bug against usually for the component fedup. Include any useful details about the system's configuration, and note that your result is part of this Test Day and mention that you followed the instructions on this page.
If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. In the 'Results' column, you can link to bug reports of any failed tests, and very briefly summarize your results. Please don't post long comments here, it will make the table hard to read: anything longer than a few words is likely fodder for a bug report, or mailing list post, or you can use <ref>comment</ref> to make the comment appear as a footnote below the table.
|Sample User||2 pass 2 fail, RHBZ #12345 RHBZ #54321|
|Petr Schindler||tested UEFI/BIOS, encrypted/non-encrypted, Server/Workstation 21, works fine - found RHBZ #1213868, met RHBZ #1209941|
|langdon||tested UEFI, encrypted, Workstation 21, works fine - met RHBZ #1209941 and attached screenshot, although evo-data-server just threw an error|
|Matthew Bunt||tested UEFI, non-encrypted, Workstation 21, real install with many packages. Found RHBZ #1209941 but upgrade was successful|
|juliuxpigface||Tested FedUp (version 0.9.0) on Fedora 'Non-Product' 21 (x86_64). Met RHBZ #1209941, but after ctrl+alt+del everything worked.|
|satellit||Tested fedup/0.9.2/1.fc21/noarch/fedup-0.9.2-1.fc21.noarch.rpm on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 |
|satellit||Tested Fedup_0.9.1-1.fc21 on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 |
|Eric Blake||Tested fedup-0.9.2-1.fc20 on a Fedora20 VM (x86_64). Specifying --product workstation downloaded lots of files, but then failed to find GPG key. Trying again with --nogpgcheck added got further, but then complained I didn't have enough free space. After finally getting 3G free, I got a warning that "yum-3.4.3-505.fc22.noarch requires yum-3.4.3-505.fc22.noarch" which looks weird, but it let me reboot to upgrade (RHBZ #1214931). After reboot, I met with display corruption (RHBZ #1214830), as well as a hang rather than reboot after all packages were updated and file systems were unmounted (RHBZ #1209941). Once I got F22 booting, the initial gdm screen had no mouse cursor (I could still move the mouse until something highlights, and then click, but it's hard to move without seeing a cursor); the cursor returned once it logged in to the normal session. A 'dnf update' succeeded once I was booted, but trying 'yum' in F22 has a missing newline (RHBZ #1214839).|
|Abdel Martínez||Tested fedup-0.9.2-1.fc21 on a Fedora Live Workstation 21 (x86_64) virtual machine on VirtualBox. Met a warning RHBZ #1214130 and finally RHBZ #1209941, but CRTL+ALT+DEL solved it.|
|juliuxpigface||Tried fedup-0.9.2-1.fc20 on a Fedora 20 KVM guest (Mate Spin, x86_64) specifying --product=nonproduct. As Eric, I found GPG Key error. I opened a report here: RHBZ #1214150. EDIT: Met RHBZ #1209941 too.|
|satellit||Tested Fedup_0.9.1-1.fc21 on Fedora Plasma-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 RHBZ #1214397|
|satellit||Tested Fedup-Plasma netinstall 20 to --network 22(Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 |
|satellit||Tested Fedup-Plasma netinstall 20 to --network 21 Then fedup --network22 (Virtualbox 15GB HD) (x86_64). Met on 2nd (fedup --network22 from 21) RHBZ #1209941 |
|satellit||Tested Fedup-workstation netinstall 20 to --network 22 --product=workstation --nogpgcheck (f22 Virtual Machine Manager) (x86_64). Met RHBZ #1209941|
- ↑ firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG
- ↑ http://wiki.sugarlabs.org/go/File:Fedup_0.9.1-1.fc21.JPG
- ↑ No software update in system settings/extra items do dnf install @kde-desktop to add plasma-pk-updates
- ↑ adds software updates to f22: https://admin.fedoraproject.org/updates/apper-0.9.1-8.fc22
- ↑ boot failed with pop up "cannot open /usr/share/kd4/apps/kdm/themes/f21"
- ↑ booted fine No auto updates: use dnf install plasma-pk-updates; reboot and it is present