Test Day:2010-04-29 Preupgrade: Difference between revisions

Latest revision as of 19:36, 26 June 2015

DATE	TIME	WHERE
2010-04-29	All day	#fedora-test-day (webirc)

What to test?[edit]

Today's installment of Fedora Test Day will focus on Preupgrade

Who's available[edit]

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

Development - Richard Hughes (IRC: hughsie)
Quality Assurance - He Rui (IRC: rhe)

Prerequisite for Test Day[edit]

A F11 or F12 system on bare metal or virtual machine
Network connection
The following packages updates installed
preupgrade-1.1.5-1.fc12 - To install, type: su -c 'yum --enablerepo=updates-testing update preupgrade'

python-urlgrabber-3.9.1-4.1.fc12 - available for download at http://kojipkgs.fedoraproject.org/packages/python-urlgrabber/3.9.1/4.1.fc12/noarch/python-urlgrabber-3.9.1-4.1.fc12.noarch.rpm

How to test?[edit]

Follow the test cases below to preupgrade your existing fedora 11 or 12 system.

Test Cases[edit]

Test Results[edit]

If you have problems with any of the tests, report a bug to Bugzilla usually for the component preupgrade. If you are unsure about exactly how to file the report or what 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, and the second should describe the hardware (monitor, and optionally printer, scanner and colorimeter) you used to test. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

User	Smolt Profile	preupgrade	preupgrade older release	low space for download	low space for install	References
User:FasUser	HW	pass	warn ^[1]	fail ^[2]	fail ^[1]	↑ ^1.0 ^1.1 RHBZ #12345 ↑ See RHBZ #12345
User:Rhe	kvm guest	fail ^[1] ^[2] ^[3]	none	fail ^[4] ^[5]	fail ^[4] ^[5]	↑ 1. Report 'Ready to being upgrade' despite having run out of room RHBZ #577436 ↑ 2. Fail to warn about low space on /boot RHBZ #573451 ↑ 3. Kickstart install failed after rebootRHBZ #587185 ↑ ^4.0 ^4.1 RHBZ #577436 ↑ ^5.0 ^5.1 RHBZ #573451
jlaska	KVM guest	pass ^[1] pass ^[2]	pass ^[3]	none	fail ^[4]	↑ ext3 '/' and 500M '/boot' ↑ ext4 '/' and 500M '/boot' ↑ RAID0 '/' and 500M '/boot' ↑ F-11 -> F-13 (Branch) fails ... does not create a kickstart file for use with upgrade
kparal	KVM guest	warn ^[1] ^[2]	none	fail ^[3] ^[4]	pass ^[5]	↑ Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault. ↑ My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM? ↑ RHBZ #587610 ↑ RHBZ #587627 ↑ Used bigger /boot than 200M (not possible with that), but simulated the test case idea with some filler files
gnat	HW	none	none	fail ^[1]	none	↑ See RHBZ #587378
Austin	HW	none	none	fail ^[1]	none	↑ See RHBZ #587378
Juan Rodriguez	Laptop	fail ^[1]^[2]	none	none	none	↑ Got hit with RHBZ #587478 ↑ Then with RHBZ #587185#c4
ericb	KVM guest	warn ^[1] ^{[long 1]}	none	warn ^[2]	fail ^{[long 2]}	↑ Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit ↑ Attempt to download rawhide failed with no more mirrors to try; not sure if it was related to the expected disk full error
gui1ty	HW	fail ^[1] ^[2]	none	none	none	↑ See RHBZ #587414 ↑ See RHBZ #587427
User:ivancjimenez	HW	fail ^[1]	none			↑ RHBZ #587185
User:japafi	VirtualBox guest	fail ^{[long 3]}HW	none	warn ^{[long 4]}	none HW

Long comments[edit]

↑ RHBZ #567978 - On first reboot, NetworkManager failed to detect network with both IPv4 and v6 requested, but worked fine with just IPv4 requested. Upgrade succeeded via network install.img.
↑ After cleanup, df -h /boot reported 155M available, but preupgrade failed to download Fedora 13 branched with warning of checksum failure downloading vmlinuz; looks like RHBZ #587610
↑ /boot partition as set by default install (198337 1K-blocks/164751 available), but preupgrade still complained that install.img didn't fit. At that time there was 132257 1K blocks available
↑ Did the test with non-default /boot (400M). Adjusted available disk space accordingly. Got error message on "no more mirrors to try" when disk was full (Step #7 on the test case). The error message could be more accurate as the problem was not about network error, but disk space. Other than that, I would consider this as PASS.

[bz12345-1] 1.0 ^1.1 RHBZ #12345

[2] See RHBZ #12345

[3] 1. Report 'Ready to being upgrade' despite having run out of room RHBZ #577436

[4] 2. Fail to warn about low space on /boot RHBZ #573451

[5] 3. Kickstart install failed after rebootRHBZ #587185

[bz577436-6] 4.0 ^4.1 RHBZ #577436

[bz573451-7] 5.0 ^5.1 RHBZ #573451

[8] xt3 '/' and 500M '/boot'

[9] xt4 '/' and 500M '/boot'

[10] RAID0 '/' and 500M '/boot'

[11] F-11 -> F-13 (Branch) fails ... does not create a kickstart file for use with upgrade

[12] Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault.

[13] My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM?

[bz587610-14] RHBZ #587610

[bz587627-15] RHBZ #587627

[16] Used bigger /boot than 200M (not possible with that), but simulated the test case idea with some filler files

[17] See RHBZ #587378

[18] See RHBZ #587378

[19] Got hit with RHBZ #587478

[20] Then with RHBZ #587185#c4

[21] Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit

[23] Attempt to download rawhide failed with no more mirrors to try; not sure if it was related to the expected disk full error

[25] See RHBZ #587414

[26] See RHBZ #587427

[bz587185-27] RHBZ #587185

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[1]

[2]

[3]

[4]

[1]

[2]

[3]

[4]

[5]

[1]

[1]

[1]

[2]

[1]

[long 1]

[2]

[long 2]

[1]

[2]

[1]

[long 3]

[long 4]

@@ Line 67: / Line 67: @@
 |-
 | [[User:jlaska|jlaska]]
-| KVM guest (ext3 {{filename|/}} partition, 500M {{filename|/boot}})
+| KVM guest
-| {{result|pass}}
+| {{result|pass}} <ref>ext3 '/' and 500M '/boot'</ref> {{result|pass}} <ref>ext4 '/' and 500M '/boot'</ref>
+| {{result|pass}} <ref>RAID0 '/' and 500M '/boot'</ref>
+| {{result|none}}
+| {{result|fail}} <ref>F-11 -> F-13 (Branch) fails ... does not create a kickstart file for use with upgrade</ref>
+| <references/>
+|-
+| [[User:kparal|kparal]]
+| KVM guest
+| {{result|warn}} <ref>Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault.</ref> <ref>My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM?</ref>
+| {{result|none}}
+| {{result|fail||587610|587627}}
+| {{result|pass}} <ref>Used bigger /boot than 200M (not possible with that), but simulated the test case idea with some filler files</ref>
+| <references/>
+|-
+| [[User:gnat|gnat]]
+| [http://www.smolts.org/client/show/pub_279eb480-a6d3-4f6b-ada8-037ffc3ae5ef HW]
+| {{result|none}}
+| {{result|none}}
+| {{result|fail}} <ref>See {{bz|587378}}</ref>
+| {{result|none}}
+| <references/>
+|-
+| [[User:austinacton|Austin]]
+| [http://smolts.org/show?uuid=pub_33c3392a-f2b9-4878-8957-ba2aa27dac36 HW]
 | {{result|none}}
 | {{result|none}}
+| {{result|fail}} <ref>See {{bz|587378}}</ref>
 | {{result|none}}
 | <references/>
 |-
-| [[User:jlaska|jlaska]]
+| [[User:Nushio|Juan Rodriguez]]
-| KVM guest (ext4 {{filename|/}} partition, 500M {{filename|/boot}})
+| [http://www.smolts.org/client/show/pub_c69221e0-c6a2-4246-9de0-435db2637b95 Laptop]
-| {{result|pass}}
+| {{result|fail}} <ref>Got hit with {{bz|587478}}</ref><ref>Then with {{bz|587185#c4}}</ref>
 | {{result|none}}
+| {{result|none}}
 | {{result|none}}
+| <references/>
+|-
+| [[User:ericb|ericb]]
+| [http://smolts.org/client/show/pub_09370914-5864-4224-92c9-d70e0ceb3eab KVM guest]
+| {{result|warn}} <ref>Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit</ref> <ref group="long">{{bz|567978}} - On first reboot, NetworkManager failed to detect network with both IPv4 and v6 requested, but worked fine with just IPv4 requested.  Upgrade succeeded via network install.img.</ref>
 | {{result|none}}
+| {{result|warn}} <ref>Attempt to download rawhide failed with no more mirrors to try; not sure if it was related to the expected disk full error</ref>
+| {{result|fail}} <ref group="long">After cleanup, df -h /boot reported 155M available, but preupgrade failed to download Fedora 13 branched with warning of checksum failure downloading vmlinuz; looks like {{bz|587610}}</ref>
 | <references/>
 |-
-| [[User:kparal|kparal]]
+| [[User:gui1ty|gui1ty]]
-| KVM guest
+| [http://www.smolts.org/client/show/pub_7e687bea-4149-41e9-bccb-fc9978028ea5 HW]
-| {{result|warn}} <ref>Works on 500M /boot, not enough space on 200M /boot - not preupgrade's fault.</ref> <ref>My mouse pointer is stuck while upgrading in anaconda. Re-occurring issue about frozen input devices in KVM?</ref>
+| {{result|fail}} <ref>See {{bz|587414}}</ref> <ref>See {{bz|587427}}</ref>
 | {{result|none}}
+| {{result|none}}
 | {{result|none}}
+| <references/>
+|-
+| [[User:ivancjimenez]]
+| [http://www.smolts.org/client/show/pub_f61057df-ca59-41d7-933a-850d3b6a114d HW]
+|{{result|fail||587185}}
 | {{result|none}}
+|
+|
 | <references/>
 |-
+| [[User:japafi]]
+| VirtualBox guest
+| {{result|fail}} <ref group="long">/boot partition as set by default install (198337 1K-blocks/164751 available), but preupgrade still complained that install.img didn't fit. At that time there was 132257 1K blocks available</ref>[http://www.smolts.org/client/show/pub_6f381837-cc13-457d-bb37-8fa97cea2a54 HW]
+| {{result|none}}
+| {{result|warn}} <ref group="long">Did the test with non-default /boot (400M). Adjusted available disk space accordingly. Got error message on "no more mirrors to try" when disk was full (Step #7 on the test case). The error message could be more accurate as the problem was not about network error, but disk space. Other than that, I would consider this as PASS.</ref>
+| {{result|none}} [http://www.smolts.org/client/show/pub_6f381837-cc13-457d-bb37-8fa97cea2a54 HW]
+| <references/>
 |}
+== Long comments ==
+<references group="long" />
+ [[Category:Fedora 13 Test Days]]

Search