Bug 688761 - 2011-03-17 Testday for Preupgrade failure for f14->f15
2011-03-17 Testday for Preupgrade failure for f14->f15
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: preupgrade (Show other bugs)
15
i686 Mac OS
unspecified Severity high
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-03-17 18:37 EDT by Richard Vijay
Modified: 2012-02-02 04:29 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-02 04:29:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Richard Vijay 2011-03-17 18:37:11 EDT
Description of problem:
2011-03-17 Testday for Preupgrade failure for f14->f15

Version-Release number of selected component (if applicable):

preupgrade-1.1.9-1.fc14.noarch
How reproducible:
Require Intel i7 Mac OS snow leap, attempt on 32bit fedora 14 install upgrade with this test day pack.
I used parellels, Attempted 5 times, I have my uuid pub_b997f715-39e9-4a12-96ca-0b6d4c8d89d0
I should tell you I have a sucessfully installed alpha on a different seperate f15 64 bit installation in same config  machine
Steps to Reproduce:
1.Install fedora 14 and update it
2.Package Preupgrade installed
3.after successfully installing F15 components Reboot is requested
4.Reboot turns to blue screen with request for network information asking for IPv4/IPV5
5. What ever you try finally upgrade collapses and askes us to apply ctrl c to break
6. goes back to f14
  
Actual results:
failure to upgrade, unexpected question on blus screen after reboot on network ipv4/ipv6

Expected results:
smooth upgrade

Additional info:
Comment 1 Richard Vijay 2011-03-17 18:38:11 EDT
my wikipage is Richardvj11 if you need additional info

Note You need to log in before you can comment on or make changes to this bug.