From Fedora Project Wiki

(fix category membership)
(Drop direct Test Days category membership)
 
(34 intermediate revisions by 15 users not shown)
Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on '''FedUp'''
Today's instalment of Fedora Test Day will focus on [[FedUp]], the Fedora system upgrade tool.


== Who's available ==
== Who's available ==


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Development - [[User:Wwoods|Will Woods]] (wwoods)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
* Quality Assurance - [[User:Adamwill|Adam Williamson]] (adamw), [[User:Pschindler|Petr Schindl]] (pschindl)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?
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.


* Usb key
== How to test? ==
* Usb externally connected HD IDE/SATA
* Empty HD IDE/SATA/SCSI
* Free space on HD


Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
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):


* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
yum --enablerepo=updates-testing install fedup
yum --enablerepo=updates-testing update fedup


== How to test? ==
{{admon/important|Check for 0.9.2-1|The newest build of fedup - 0.9.2-1 - was pushed to the mirrors only recently. The above command ''should'' install it, but please make sure that fedup-0.9.2-1 is installed after running it. If you got an older version (perhaps because of a mirror that has not yet synced) please download and install the updated version directly:
* [https://kojipkgs.fedoraproject.org/packages/fedup/0.9.2/1.fc20/noarch/fedup-0.9.2-1.fc20.noarch.rpm fedup-0.9.2-1.fc20.noarch.rpm] (Fedora 20)
* [https://kojipkgs.fedoraproject.org/packages/fedup/0.9.2/1.fc21/noarch/fedup-0.9.2-1.fc21.noarch.rpm fedup-0.9.2-1.fc21.noarch.rpm] (Fedora 21)}}


High level details on how a contributor can get involved.  This can include (but not limited to):
To upgrade, run (F21):


* Areas to target with exploratory testing
fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os
* A list of pre-defined test cases to execute
* How to report back results


Here's another common chunk (again, replace XX as above):
or (F20):


=== '''Update your machine''' ===
fedup --network 22 --product (product) --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os


If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
where {{code|(arch)}} is the appropriate architecture (armhfp, x86_64, or i386) and {{code|(product)}} is the most appropriate 'product' for the install - see [[FedUp#Important_Changes_in_the_Upgrade_process_to_Fedora_21|this note]].


=== '''Live image''' ===
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.


Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
If the upgrade completes successfully, test the upgraded system to ensure it works correctly.
 
== Test Cases ==
 
Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].


== Test Results ==
== Test Results ==


Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If any of your upgrades fails (or leads to a broken system), report a bug to [https://bugzilla.redhat.com 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 [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=fedup 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 have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
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 {{code|<nowiki><ref>comment</ref></nowiki>}} to make the comment appear as a footnote below the table.


{|
{| class="wikitable" width=100%
! User
! User
! [[QA:Testcase_sample_1|Sample test 1]]
! Results
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_sample_4|Sample test 4]]
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| {{result|none}}  
| 2 pass 2 fail, {{bz|12345}} {{bz|54321}}
| {{result|pass}}
|-
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| [[User: pschindl|Petr Schindler]]
| {{result|fail}} <ref>{{bz|12345}}</ref>
| tested UEFI/BIOS, encrypted/non-encrypted, Server/Workstation 21, works fine - found {{bz|1213868}}, met {{bz|1209941}}
| <references/>
|-
| [[User: langdon|langdon]]
| tested UEFI, encrypted, Workstation 21, works fine - met {{bz|1209941}} and attached screenshot, although evo-data-server just threw an error
|-
| [[User: darakus|Matthew Bunt]]
| tested UEFI, non-encrypted, Workstation 21, real install with many packages. Found {{bz|1209941}} but upgrade was successful
|-
| [[User: juliuxpigface|juliuxpigface]]
| Tested FedUp (version 0.9.0) on Fedora 'Non-Product' 21 (x86_64). Met {{bz|1209941}}, but after ctrl+alt+del everything worked.
|-
| [[User: satellit|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 {{bz|1209941}} <ref>firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG</ref>
|-
| [[User: satellit|satellit]]
| Tested Fedup_0.9.1-1.fc21 on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>http://wiki.sugarlabs.org/go/File:Fedup_0.9.1-1.fc21.JPG</ref>
|-
| [[User: ericb|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 ({{bz|1214931}}). After reboot, I met with display corruption ({{bz|1214830}}), as well as a hang rather than reboot after all packages were updated and file systems were unmounted ({{bz|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 ({{bz|1214839}}).
|-
| [[User:potty|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 {{bz|1214130}} and finally {{bz|1209941}}, but CRTL+ALT+DEL solved it.
|-
| [[User: juliuxpigface|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: {{bz|1214150}}. EDIT: Met {{bz|1209941}} too.
|-
| [[User: satellit|satellit]]
| Tested Fedup_0.9.1-1.fc21 on Fedora Plasma-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>No software update in  system settings/extra items do dnf install @kde-desktop to add plasma-pk-updates</ref>{{bz|1214397}}<ref>adds software updates to f22: https://admin.fedoraproject.org/updates/apper-0.9.1-8.fc22</ref>
|-
| [[User: satellit|satellit]]
| Tested Fedup-Plasma netinstall 20 to --network 22(Virtualbox 15GB HD) (x86_64). Met {{bz|1209941}} <ref>boot failed with pop up "cannot open /usr/share/kd4/apps/kdm/themes/f21"</ref>
|-
| [[User: satellit|satellit]]
| Tested Fedup-Plasma netinstall 20 to --network 21 Then fedup --network22 (Virtualbox 15GB HD) (x86_64). Met on 2nd (fedup --network22 from 21) {{bz|1209941}} <ref>booted fine No auto updates: use dnf install plasma-pk-updates; reboot and it is present</ref>
|-
| [[User: satellit|satellit]]
| Tested Fedup-workstation netinstall 20 to --network 22 --product=workstation --nogpgcheck (f22 Virtual Machine Manager) (x86_64). Met  {{bz|1209941}}
|-
|-
|}
|}
<references/>


[[Category:Fedora 22 Test Days]]
[[Category:Fedora 22 Test Days]]

Latest revision as of 19:40, 26 June 2015

Fedora Test Days
FedUp
Date 2015-04-21
Time all day
Website QA/Fedora_22_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today's instalment of Fedora Test Day will focus on FedUp, the Fedora system upgrade tool.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day[edit]

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?[edit]

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
Check for 0.9.2-1
The newest build of fedup - 0.9.2-1 - was pushed to the mirrors only recently. The above command should install it, but please make sure that fedup-0.9.2-1 is installed after running it. If you got an older version (perhaps because of a mirror that has not yet synced) please download and install the updated version directly:

To upgrade, run (F21): 

fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os

or (F20): 

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.

Test Results[edit]

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.

User Results
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 [1]
satellit Tested Fedup_0.9.1-1.fc21 on Fedora workstation-netinstall 21 (Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 [2]
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 [3]RHBZ #1214397[4]
satellit Tested Fedup-Plasma netinstall 20 to --network 22(Virtualbox 15GB HD) (x86_64). Met RHBZ #1209941 [5]
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 [6]
satellit Tested Fedup-workstation netinstall 20 to --network 22 --product=workstation --nogpgcheck (f22 Virtual Machine Manager) (x86_64). Met RHBZ #1209941
  1. ↑ firefox is mistagged as f21: http://wiki.sugarlabs.org/go/File:Dnf_update.JPG
  2. ↑ http://wiki.sugarlabs.org/go/File:Fedup_0.9.1-1.fc21.JPG
  3. ↑ No software update in system settings/extra items do dnf install @kde-desktop to add plasma-pk-updates
  4. ↑ adds software updates to f22: https://admin.fedoraproject.org/updates/apper-0.9.1-8.fc22
  5. ↑ boot failed with pop up "cannot open /usr/share/kd4/apps/kdm/themes/f21"
  6. ↑ booted fine No auto updates: use dnf install plasma-pk-updates; reboot and it is present
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2015-04-21_FedUp&oldid=416664"