From Fedora Project Wiki

(drop direct test day category membership (should be via release))
 
(40 intermediate revisions by 15 users not shown)
Line 19: Line 19:
== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


* A F12 or F13 system on bare metal or virtual machine
* A F-12 or F-13 system on bare metal or virtual machine
* Network connection
* Network connection
* The following packages updates installed
* The following packages updates installed:
*: {{package|preupgrade}} <!-- - To install, type: <code>su -c 'yum --enablerepo=updates-testing update preupgrade'</code> -->
* {{package|preupgrade}}  
*: {{package|python-urlgrabber}} <!-- - 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 -->
** F-12: <code>preupgrade-1.1.7-1.fc12.noarch</code>
** F-13: The newest version is available at http://people.freedesktop.org/~hughsient/fedora/13/i386.  A scratch build is available for Fedora 13.  You can install it by:
:<pre>
: # su -c 'yum --nogpgcheck localinstall "http://koji.fedoraproject.org/koji/getfile?taskID=2442952&name=preupgrade-1.1.7-0.20.20100902git.fc13.noarch.rpm"'
:</pre>
* {{package|python-urlgrabber}}  
** F-12: <code>python-urlgrabber-3.9.1-4.2.fc12.noarch</code>
** F-13: The newest version is <code>python-urlgrabber-3.9.1-7.fc13</code>, install it by:
:<pre>
: # su -c 'yum --enablerepo=updates-testing update python-urlgrabber'
:</pre>


== How to test? ==
== How to test? ==
Line 31: Line 41:
=== Test Cases ===
=== Test Cases ===


* [[QA:Testcase_Preupgrade]] - ''Enough /boot space for download and install''
* [[QA:Testcase_Preupgrade]] - ''Enough /boot space to download and install''
* [[QA:Testcase_Preupgrade_from_older_release]] - ''Not enough /boot space for download''
* [[QA:Testcase_Preupgrade_from_older_release]] - ''Not enough /boot space to download''
* [[QA:Testcase_Preupgrade_cli]] - ''Preupgrade-cli and its command-line options''
* [[QA:Testcase_Preupgrade_cli]] - ''Preupgrade-cli and its command-line options''


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


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=rawhide&component=preupgrade 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 '''<nowiki>{{result|pass}}</nowiki>'''. If you had trouble, enter the word '''<nowiki>{{result|warn}}<ref>xxx</ref></nowiki>''' or '''<nowiki>{{result|fail|bug No}}</nowiki>''', 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.
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=rawhide&component=preupgrade 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 '''<nowiki>{{result|pass}}</nowiki>'''. If you had trouble, enter the word '''<nowiki>{{result|warn}}<ref>xxx</ref></nowiki>''' or '''<nowiki>{{result|fail|bug number}}</nowiki>''', 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
! User
! Smolt Profile
! [[QA:Testcase_Preupgrade|preupgrade]]  
! [[QA:Testcase_Preupgrade|preupgrade]]  
! [[QA:Testcase_Preupgrade_from_older_release|preupgrade older release]]
! [[QA:Testcase_Preupgrade_from_older_release|preupgrade older release]]
Line 48: Line 57:
|-
|-
| [[User:Example]]  
| [[User:Example]]  
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{result|pass}}
| {{result|pass}}
| {{result|warn||12345}}
| {{result|warn||12345}}
Line 54: Line 62:
| <references/>
| <references/>
|-
|-
|}
| [[apetz]]
| {{result|warn}} <ref>See {{bz|629245}}</ref>
| N/A
| N/A
| <references/>
|-
| [[User:Rhe|He Rui]]
| {{result|fail|rhe}}<ref>failed with preupgrade-1.1.4-1.fc13, seems stage= and ks= are not honorred {{bz|624971}}</ref>
| {{result|fail|rhe|624971}}
| {{result|fail|rhe}}<ref>ks= is not honorred {{bz|624971}}</ref>
| <references/>
|-
| [[User:newgle1|newgle1]]
| {{result|fail|newgle1|629245}}
| {{result|fail|newgle1|624971}}
| {{result|fail|newgle1|629245}}
| <references/>
|-
| [[User:jamesni|James Ni]]
| {{result|fail|jamesni}}<ref>failed with preupgrade-1.1.6-1.fc13, adds extra spaces to grub.conf {{bz|592345}}, anaconda can't find install.img {{bz|624971}}</ref>
| N/A
| N/A
| <references/>
|-
| [[User:epico|Epico]]
| N/A
| N/A
| {{result|fail|epico}} <ref group="long">See {{bz|629245}} {{bz|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. </ref>
| <references/>
|-
| [[User:jlaska|jlaska]]
| {{result|fail}} <ref name="bz624971">{{bz|624971}} - unable to locate install.img or ks.cfg using UUID=xxxxx</ref> <ref>Tested with <code>preupgrade-1.1.7-0.20.20100902git.fc13</code></ref>
| {{result|fail}} <ref name="bz624971"/>
| {{result|fail}} <ref name="bz624971"/>
| <references/>
|-
| [[User:ericb|Eric Blake]]
| {{result|warn}} <ref name="bz629738">{{bz|629738}} - no support for --help/--version</ref> <ref name="bz629745">{{bz|629745}} - bogus exit status</ref> <ref name="eblake1">VM ran out of space in /var/cache/yum; preupgrade correctly detected this; retry with a larger VM succeeded</ref> <ref name="bz624971">{{bz|624971}} - just like others, I had to change UUID to /dev/vda1 to tell Anaconda where to look</ref> <ref name="eblake2">The preupgrade/anaconda process completed and rebooted automatically, but with NetworkManager stopped; I had to manually start it before I could access the Internet</ref>
| {{result|fail}} <ref name="bz629814">{{bz|629814}} - preupgrade finished with VM having barely enough space, but anaconda failed claiming that there was insufficient space to complete the transaction. Retrying with a larger VM disk succeeded.</ref> <ref name="eblake2"/>
| {{result|warn}} <ref name="bz624971"/> <ref name="bz629890">{{bz|629890}} - The reboot after preupgrade-cli is not automated</ref> <ref name="eblake2"/>
| <references/>
|-
| [[User:RoyBoy626]]
| {{result|none}}
| {{result|pass}}<ref name="one"> changed default /images/install.img as noted by Epico. Cross preupgrade from f12.i686 to f14.x86_64. fedora icon with 13 displayed in GUI. Confusing. Had three 250GB disk with only SCSI ID diff...Had to guess in anaconda which was to be target. Had prob with restart of preupgrade. Will file bug report.</ref>
| {{result|none}}
| <references/>
|-
| [[User:maxamillion|Adam Miller]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| These were all done in KVM virtual machines with 1GB of ram and what appears to be plenty of space in /boot so my tests might have been skewed, but I didn't encounter any issues.<references/>
|-
| [[User:dramsey|David Ramsey]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| Also done with virtual machines.
|-|}
 


== Long comments ==
<references group="long" />


[[Category:Fedora 14 Test Days]]
[[Category:Fedora 14 Test Days]]

Latest revision as of 23:55, 18 June 2015

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

What to test?[edit]

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

Prerequisite for Test Day[edit]

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

Follow the test cases below to preupgrade your existing fedora 12 or 13 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 {{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.

Long comments[edit]

  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.
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]
Fail fail newgle1 [2]
Fail fail newgle1 [1]
  1. 1.0 1.1 RHBZ #629245
  2. RHBZ #624971
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
[long 1]
jlaska
Fail fail
[1] [2]
Fail fail
[1]
Fail fail
[1]
  1. 1.0 1.1 1.2 RHBZ #624971 - unable to locate install.img or ks.cfg using UUID=xxxxx
  2. Tested with preupgrade-1.1.7-0.20.20100902git.fc13
Eric Blake
Warning warn
[1] [2] [3] [4] [5]
Fail fail
[6] [5]
Warning warn
[4] [7] [5]
  1. RHBZ #629738 - no support for --help/--version
  2. RHBZ #629745 - bogus exit status
  3. VM ran out of space in /var/cache/yum; preupgrade correctly detected this; retry with a larger VM succeeded
  4. 4.0 4.1 RHBZ #624971 - just like others, I had to change UUID to /dev/vda1 to tell Anaconda where to look
  5. 5.0 5.1 5.2 The preupgrade/anaconda process completed and rebooted automatically, but with NetworkManager stopped; I had to manually start it before I could access the Internet
  6. RHBZ #629814 - preupgrade finished with VM having barely enough space, but anaconda failed claiming that there was insufficient space to complete the transaction. Retrying with a larger VM disk succeeded.
  7. RHBZ #629890 - The reboot after preupgrade-cli is not automated
User:RoyBoy626
none
Pass pass
[1]
none
  1. changed default /images/install.img as noted by Epico. Cross preupgrade from f12.i686 to f14.x86_64. fedora icon with 13 displayed in GUI. Confusing. Had three 250GB disk with only SCSI ID diff...Had to guess in anaconda which was to be target. Had prob with restart of preupgrade. Will file bug report.
Adam Miller
Pass pass
Pass pass
Pass pass
These were all done in KVM virtual machines with 1GB of ram and what appears to be plenty of space in /boot so my tests might have been skewed, but I didn't encounter any issues.
David Ramsey
Pass pass
Pass pass
Pass pass
Also done with virtual machines.