Test Day:2010-04-29 Preupgrade

From FedoraProject

Revision as of 13:04, 14 June 2013 by Peter (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
DATE TIME WHERE
2010-04-29 All day #fedora-test-day (webirc)

Contents

[edit] What to test?

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

[edit] Who's available

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

[edit] Prerequisite for Test Day

[edit] How to test?

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

[edit] Test Cases

[edit] 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 pass
Warning warn [1]
Fail fail
[2]
Fail fail [1]
  1. 1.0 1.1 RHBZ #12345
  2. See RHBZ #12345
User:Rhe kvm guest
Fail fail

[1] [2] [3]

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