Bug 750216

Summary: cannot boot into F16 after preupgrading from F15 to F16
Product: [Fedora] Fedora Reporter: Hongqing Yang <hoyang>
Component: preupgradeAssignee: Richard Hughes <hughsient>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: awilliam, hughsient, mads, robatino
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-01 02:18:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda logs
none
grub conf
none
grub conf
none
ks file genereated by preupgrade none

Description Hongqing Yang 2011-10-31 11:28:45 UTC
Created attachment 530952 [details]
anaconda logs

Description of problem:
after preupgrading from F15 to F16, the grub2.cfg links to /boot/grub2/grub.cfg, the /boot/grub2/ directory does not exist.
after modify grub.cfg to boot from 'Upgrade to Fedora 16 Branched Pre-release(Verne)', it still cannot not boot.

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


How reproducible:

100%

Steps to Reproduce:
1. install F15
2. install preupgrade 1.1.10_1
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Hongqing Yang 2011-10-31 11:55:10 UTC
Created attachment 530957 [details]
grub conf

Comment 2 Hongqing Yang 2011-10-31 12:18:49 UTC
Created attachment 530963 [details]
grub conf

Comment 3 Hongqing Yang 2011-10-31 12:28:36 UTC
Created attachment 530965 [details]
ks file genereated by preupgrade

Comment 4 Hongqing Yang 2011-10-31 12:40:42 UTC
(In reply to comment #0)
> Created attachment 530952 [details]
> anaconda logs
> 
> Description of problem:
> after preupgrading from F15 to F16, the grub2.cfg links to
> /boot/grub2/grub.cfg, the /boot/grub2/ directory does not exist.
> after modify grub.cfg to boot from 'Upgrade to Fedora 16 Branched
> Pre-release(Verne)', it still cannot not boot.
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 100%
> 
> Steps to Reproduce:
> 1. install F15
> 2. install preupgrade 1.1.10_1
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

Correct the description:
there is only grub.cfg under /etc, there is no grub2.cfg. 
and all anaconda logs in /var/log/ are not touched.
after installation , the preupgrade directory under root / is empty.

Comment 5 Mads Kiilerich 2011-10-31 13:40:01 UTC
This indicates that 
1: the old f15 kernels has been removed
2: grub2 wasn't installed
3: anaconda didn't finish correctly

One way to investigate it further could be to look for anaconda log files in /tmp while upgrading.

Comment 6 Adam Williamson 2011-10-31 16:00:28 UTC
hong: preupgrade is a two-step process: once you install preupgrade into F15, then run it and let it download all the upgrade packages, you're supposed to reboot and it boots into anaconda to complete the upgrade. That's what the 'Upgrade to Verne' bootloader entry is for.

When you say "after modify grub.cfg to boot from 'Upgrade to Fedora 16 Branched
Pre-release(Verne)', it still cannot not boot.", what do you mean exactly?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Hongqing Yang 2011-11-01 02:18:22 UTC
(In reply to comment #6)
> hong: preupgrade is a two-step process: once you install preupgrade into F15,
> then run it and let it download all the upgrade packages, you're supposed to
> reboot and it boots into anaconda to complete the upgrade. That's what the
> 'Upgrade to Verne' bootloader entry is for.
> 
> When you say "after modify grub.cfg to boot from 'Upgrade to Fedora 16 Branched
> Pre-release(Verne)', it still cannot not boot.", what do you mean exactly?
> 
> 
> 
> -- 
> Fedora Bugzappers volunteer triage team
> https://fedoraproject.org/wiki/BugZappers

yeah, it is not a bug. It was F16 when I come this morning.