From Fedora Project Wiki

m (Corrected wiki)
Line 98: Line 98:
| <references/>
| <references/>
|-
|-
| [[User:FIXME]]
| [[User:ericb|Eric Blake]]
| {{result|none}}
| {{result|none}} <ref name="629738">{{bz|629738}} - no support for --help/--version</ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Revision as of 20:21, 2 September 2010

DATE TIME WHERE
2010-09-02 All day #fedora-test-day (webirc)

What to test?

Today's installation 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 ...

Prerequisite for Test Day

  • A F-12 or F-13 system on bare metal or virtual machine
  • Network connection
  • The following packages updates installed:
  • preupgrade
# su -c 'yum --nogpgcheck localinstall "http://koji.fedoraproject.org/koji/getfile?taskID=2442952&name=preupgrade-1.1.7-0.20.20100902git.fc13.noarch.rpm"'
  • python-urlgrabber
    • F-12: python-urlgrabber-3.9.1-4.2.fc12.noarch
    • F-13: The newest version is python-urlgrabber-3.9.1-7.fc13, install it by:
# su -c 'yum --enablerepo=updates-testing update python-urlgrabber'

How to test?

Follow the test cases below to preupgrade your existing fedora 12 or 13 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 {{result|pass}}. If you had trouble, enter the word {{result|warn}}<ref>xxx</ref> or {{result|fail|bug number}}, 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 preupgrade preupgrade older release preupgrade-cli References
User:Example
Pass pass
Warning warn [1]
Fail fail
[2]
  1. RHBZ #12345
  2. See RHBZ #12345
apetz
Warning warn
[1]
N/A N/A
  1. See RHBZ #629245
He Rui
Fail fail rhe
[1]
Fail fail rhe [2]
Fail fail rhe
[3]
  1. failed with preupgrade-1.1.4-1.fc13, seems stage= and ks= are not honorred RHBZ #624971
  2. RHBZ #624971
  3. ks= is not honorred RHBZ #624971
newgle1
Fail fail newgle1 [1]
none
none
  1. RHBZ #629245
James Ni
Fail fail jamesni
[1]
N/A N/A
  1. failed with preupgrade-1.1.6-1.fc13, adds extra spaces to grub.conf RHBZ #592345, anaconda can't find install.img RHBZ #624971
Epico N/A N/A
Fail fail epico
[1]
  1. See RHBZ #629245 RHBZ #624971, replace UUID=xxxxxx with /dev/sda1 for stage2 and ks in grub.conf, it starts to work. also need to replace /images/install.img with /upgrade/install.img in anaconda.
jlaska
Fail fail
Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title [1]
Fail fail
Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title
Fail fail
Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title
  1. Tested with preupgrade-1.1.7-0.20.20100902git.fc13
Eric Blake
none
Cite error: Invalid <ref> tag; name cannot be a simple integer. Use a descriptive title
none
none
User:FIXME
none
none
none