2010-04-29 Preupgrade

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

What to test?

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

Who's available

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

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?

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

Test Cases

Test Results

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	none	none	↑ 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?
gnat	HW	none	none	fail ^[1]	none	↑ See RHBZ #587378
Juan Rodriguez	I.O.U.	none	none	none	none
ericb	KVM guest	none ^[1]	none	none	none	↑ Manually pruned 200M /boot from three down to one kernel, but preupgrade still complained that install.img didn't fit; upgrade still in process...

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

[14] See RHBZ #587378

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

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[1]

[2]

[3]

[4]

[1]

[2]

[1]

[1]

Search

Test Day:2010-04-29 Preupgrade

Contents