Bug 881764 - fedup F17 to F18 upgrade failure
Summary: fedup F17 to F18 upgrade failure
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-29 14:34 UTC by Germano Massullo (Thetra)
Modified: 2013-01-03 05:25 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-12 20:57:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fedup.log (315.16 KB, text/plain)
2012-12-01 08:53 UTC, Germano Massullo (Thetra)
no flags Details
noFeedback during upgrade (26.27 KB, image/png)
2012-12-03 18:16 UTC, Germano Massullo (Thetra)
no flags Details
Fedora stuck (27.20 KB, image/png)
2012-12-03 18:16 UTC, Germano Massullo (Thetra)
no flags Details
grub (78.67 KB, image/png)
2012-12-06 16:13 UTC, Germano Massullo (Thetra)
no flags Details
upgrade.log (284.42 KB, text/plain)
2012-12-11 21:35 UTC, Germano Massullo (Thetra)
no flags Details
boot screenshot (38.13 KB, image/png)
2012-12-12 09:01 UTC, Germano Massullo (Thetra)
no flags Details

Description Germano Massullo (Thetra) 2012-11-29 14:34:22 UTC
Description of problem:
I tried fedup on a VirtualBOX virtual machine. The operating system is Fedora 17 KDE 64bit.
The command I used is:
# fedup-cli --network 18

After fedup downloaded all packages, I had the following error message:

getting boot images...
Traceback (most recent call last):
  File "/usr/bin/fedup-cli", line 285, in <module>
    main(args)
  File "/usr/bin/fedup-cli", line 236, in main
    raise NotImplementedError("use --instrepo or --skipkernel")
NotImplementedError: use --instrepo or --skipkernel

Comment 1 Tim Flink 2012-11-29 19:13:59 UTC
While the error isn't completely clear in this case, the command you're using is not correct. --instrepo is required for fedup to complete

Please see the FedUp documentation on the Fedora wiki:
https://fedoraproject.org/wiki/FedUp

Comment 2 Sergio Basto 2012-11-29 21:49:58 UTC
Please add this to fedup-cli --network 18 : 
 --debuglog fedupdebug.log --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64

btw why mirrors don't have in images dir: 

initrd.img                 21-Nov-2012 14:58   26M  
upgrade.img                21-Nov-2012 14:58   26M  
vmlinuz                    21-Nov-2012 14:57  4.6M  

if so , we don't need specify --instrepo could be any mirror 

Thanks,

Comment 3 Tim Flink 2012-11-29 22:39:50 UTC
(In reply to comment #2)
> Please add this to fedup-cli --network 18 : 
>  --debuglog fedupdebug.log
> --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64

No, please don't use that - it's only meant for early testing and doesn't always contain a stable upgrade.img. Please follow the directions in the wiki page unless you're willing to deal with the potential consequences of using a less-tested upgrade mechanism. Fedup is still under development and that repo will be changing before F18 final is released.

The wiki page I'm referring to is:
https://fedoraproject.org/wiki/FedUp

> btw why mirrors don't have in images dir: 
> 
> initrd.img                 21-Nov-2012 14:58   26M  
> upgrade.img                21-Nov-2012 14:58   26M  
> vmlinuz                    21-Nov-2012 14:57  4.6M  
> 
> if so , we don't need specify --instrepo could be any mirror 

Yes, upgrade.img should be on all the mirrors carrying F18 beta and you can substitute the URLs in the docs for a more local mirror.

However, getting rid of --instrepo isn't quite so simple. The only repo that can be discovered from the F17 system is the F18 Everything repo which does not contain the upgrade.img needed for upgrade.

There is currently work going on to not require --isntrepo any more but that won't be for a little while yet as it requires some changes in mirror management and release engineering.

Comment 4 Germano Massullo (Thetra) 2012-12-01 08:53:20 UTC
Created attachment 655453 [details]
fedup.log

Comment 5 Germano Massullo (Thetra) 2012-12-02 10:46:49 UTC
I have submitted a fedup log

Comment 6 Tim Flink 2012-12-03 15:15:13 UTC
what did you use for the value passed into --instrepo?

Comment 7 Germano Massullo (Thetra) 2012-12-03 16:47:18 UTC
(In reply to comment #6)
> what did you use for the value passed into --instrepo?
I used the command:
# fedup-cli --network 18 --debuglog fedup.log --instrepo http://dl.fedoraproject.org/pub/fedora/linux/relases/test/18-Beta/Fedora/x86_64/os

Comment 8 Tim Flink 2012-12-03 16:53:01 UTC
(In reply to comment #7)
> (In reply to comment #6)
> > what did you use for the value passed into --instrepo?
> I used the command:
> # fedup-cli --network 18 --debuglog fedup.log --instrepo
> http://dl.fedoraproject.org/pub/fedora/linux/relases/test/18-Beta/Fedora/
> x86_64/os

Bah, that's in the debug log and I missed it. Sorry.

There's a typo in the link - relases should be releases

Comment 9 Germano Massullo (Thetra) 2012-12-03 18:15:58 UTC
Ok now it started, but when I rebooted the system to start the upgrade process...

1) "Upgrade system" Grub entry was not selected by default
2) During upgrade process I had no viewable feedback from the system (see attachment)
3) After the system has been upgraded, when I boot it, I get a freezed screen on Fedora boot logo (see attachment)

Comment 10 Germano Massullo (Thetra) 2012-12-03 18:16:21 UTC
Created attachment 656866 [details]
noFeedback during upgrade

Comment 11 Germano Massullo (Thetra) 2012-12-03 18:16:46 UTC
Created attachment 656867 [details]
Fedora stuck

Comment 12 Tim Flink 2012-12-03 18:38:20 UTC
(In reply to comment #9)
> Ok now it started, but when I rebooted the system to start the upgrade
> process...
> 
> 1) "Upgrade system" Grub entry was not selected by default
https://bugzilla.redhat.com/show_bug.cgi?id=879290

> 2) During upgrade process I had no viewable feedback from the system (see
> attachment)

https://bugzilla.redhat.com/show_bug.cgi?id=873144

There are workarounds in the documentation:

https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F

> 3) After the system has been upgraded, when I boot it, I get a freezed
> screen on Fedora boot logo (see attachment)

Can you check to see if this is the same symptom as https://bugzilla.redhat.com/show_bug.cgi?id=883072 ?

I'm mostly interested in whether the system-upgrade arg is still in the kernel boot args. Is your system using encrypted disks?

Comment 13 Germano Massullo (Thetra) 2012-12-03 19:03:46 UTC
The virtual machine I tried on, does not have encrypted partitions

Comment 14 Tim Flink 2012-12-05 22:58:52 UTC
(In reply to comment #13)
> The virtual machine I tried on, does not have encrypted partitions

I should have been a bit more specific on what I was asking.

Does the VM have 'systemd.unit=system-upgrade.target' in the grub entry it's trying to boot?

Comment 15 Germano Massullo (Thetra) 2012-12-06 16:12:42 UTC
(In reply to comment #14)
> (In reply to comment #13)
> Does the VM have 'systemd.unit=system-upgrade.target' in the grub entry it's
> trying to boot?

No, it does not have 'systemd.unit=system-upgrade.target' in the grub entry it's trying to boot.
See attachment

Comment 16 Germano Massullo (Thetra) 2012-12-06 16:13:08 UTC
Created attachment 658843 [details]
grub

Comment 17 Germano Massullo (Thetra) 2012-12-06 16:13:47 UTC
I forgot to say that it is Fedora KDE, not Fedora Gnome

Comment 18 Will Woods 2012-12-10 22:18:26 UTC
That GRUB screenshot is missing the last line of the boot arguments, so I can't tell if it's there or not. Can you check the contents of grub2.cfg (or attach it to the bug report)?

Also: did this system start with the original F17 release, or did you apply F17 updates before starting fedup?

Comment 19 Germano Massullo (Thetra) 2012-12-11 17:30:24 UTC
(In reply to comment #18)
> That GRUB screenshot is missing the last line of the boot arguments, so I
> can't tell if it's there or not. Can you check the contents of grub2.cfg (or
> attach it to the bug report)?
> 
> Also: did this system start with the original F17 release, or did you apply
> F17 updates before starting fedup?

If I select one of F17 grub menu entries, the system will not boot.

Here the grub.cfg




















#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
else
  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.6.7-5.fc18.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-678ef9d3-0913-4451-b851-57dd93fd546f' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
	else
	  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
	fi
	echo 'Loading Fedora (3.6.7-5.fc18.x86_64)'
	linux	/boot/vmlinuz-3.6.7-5.fc18.x86_64 root=UUID=678ef9d3-0913-4451-b851-57dd93fd546f ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0  KEYTABLE=it LANG=it_IT.UTF-8 rhgb quiet
	echo 'Loading initial ramdisk ...'
	initrd /boot/initramfs-3.6.7-5.fc18.x86_64.img
}
menuentry 'System Upgrade' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-678ef9d3-0913-4451-b851-57dd93fd546f' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
	else
	  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
	fi
	echo 'Loading System Upgrade'
	linux	/boot/upgrade/vmlinuz root=UUID=678ef9d3-0913-4451-b851-57dd93fd546f ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0  KEYTABLE=it LANG=it_IT.UTF-8 rhgb quiet systemd.unit=system-upgrade.target
	echo 'Loading initial ramdisk ...'
	initrd /boot/upgrade/upgrade.img
}
menuentry 'Fedora (3.6.6-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-678ef9d3-0913-4451-b851-57dd93fd546f' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
	else
	  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
	fi
	echo 'Loading Fedora (3.6.6-1.fc17.x86_64)'
	linux	/boot/vmlinuz-3.6.6-1.fc17.x86_64 root=UUID=678ef9d3-0913-4451-b851-57dd93fd546f ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0  KEYTABLE=it LANG=it_IT.UTF-8 rhgb quiet
	echo 'Loading initial ramdisk ...'
	initrd /boot/initramfs-3.6.6-1.fc17.x86_64.img
}
menuentry 'Fedora (3.6.2-4.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-678ef9d3-0913-4451-b851-57dd93fd546f' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
	else
	  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
	fi
	echo 'Loading Fedora (3.6.2-4.fc17.x86_64)'
	linux	/boot/vmlinuz-3.6.2-4.fc17.x86_64 root=UUID=678ef9d3-0913-4451-b851-57dd93fd546f ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0  KEYTABLE=it LANG=it_IT.UTF-8 rhgb quiet
	echo 'Loading initial ramdisk ...'
	initrd /boot/initramfs-3.6.2-4.fc17.x86_64.img
}
menuentry 'Fedora (3.5.4-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-678ef9d3-0913-4451-b851-57dd93fd546f' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  678ef9d3-0913-4451-b851-57dd93fd546f
	else
	  search --no-floppy --fs-uuid --set=root 678ef9d3-0913-4451-b851-57dd93fd546f
	fi
	echo 'Loading Fedora (3.5.4-1.fc17.x86_64)'
	linux	/boot/vmlinuz-3.5.4-1.fc17.x86_64 root=UUID=678ef9d3-0913-4451-b851-57dd93fd546f ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 rd.luks=0  KEYTABLE=it LANG=it_IT.UTF-8 rhgb quiet
	echo 'Loading initial ramdisk ...'
	initrd /boot/initramfs-3.5.4-1.fc17.x86_64.img
}
submenu 'Advanced options for Fedora Linux' $menuentry_id_option 'gnulinux-advanced-678ef9d3-0913-4451-b851-57dd93fd546f' {
}
if [ "x$default" = 'Fedora Linux, with Linux 3.3.4-5.fc17.x86_64' ]; then default='Advanced options for Fedora Linux>Fedora Linux, with Linux 3.3.4-5.fc17.x86_64'; fi;
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Comment 20 Will Woods 2012-12-11 21:12:34 UTC
I don't see anything wrong with the F18 boot entry. It's possible that there's something else going wrong here.

Can you attach the /var/log/upgrade.log from the system? If nothing went wrong during the upgrade I'm not sure how this could be fedup's fault. 

What happens if you remove 'rhgb quiet' from the boot arguments? (You may have to wait a few (5-10) minutes before any boot errors appear..)

Comment 21 Germano Massullo (Thetra) 2012-12-11 21:35:23 UTC
Created attachment 661694 [details]
upgrade.log

Comment 22 Germano Massullo (Thetra) 2012-12-12 09:01:12 UTC
Created attachment 662147 [details]
boot screenshot

NO rhgb quiet

Comment 23 Sergio Basto 2012-12-12 20:16:55 UTC
(In reply to comment #22)
> Created attachment 662147 [details]
> boot screenshot
> 
> NO rhgb quiet

I think, system boot well, but X11 doesn't start
edit grub boot entry and add "3" to boot in init 3 , see /var/log/Xorg.0.log to know why X11 doesn't start . 

BTW are you using VirtualBox from rpmfusion repos ? as maintainer of the package I advise you to use it :)

Comment 24 Germano Massullo (Thetra) 2012-12-12 20:57:15 UTC
It wasn't a Fedup bug. The Virtualmachine was simply trying to load Oracle video drivers compiled for the previous kernel. A reinstallation of VBoxGuestAdditions solved the problem :-)

Comment 25 Eric 2013-01-03 00:37:20 UTC
To resolve this issue (boot frozen at fedora logo after upgrade), which I had as well, the following steps were needed, with the guest additions ISO mounted in VirtualBox:

-Reboot the VM, hit a key to interrupt Grub2 boot loader.  We need to boot single user (run level 1), the process for which has changed from Grub 1.

-Select your kernel, hit 'e'.

-Go down to the line starting with "linux".  Hit "End".  I needed to ignore the rendering bug that did not properly show the full line of text for long entries, just type " 1".  That is "Space" followed by "1".  Then, hit "F10".

-Your system will now boot single user and give you a command prompt.

-We need to install the VirtualBox guest additions as follows:

mount /dev/cdrom /mnt
cd /mnt; ./VBoxLinuxAdditions.run
reboot

Comment 26 Sergio Basto 2013-01-03 05:25:39 UTC
(In reply to comment #25)
> To resolve this issue (boot frozen at fedora logo after upgrade), which I
> had as well, the following steps were needed, with the guest additions ISO
> mounted in VirtualBox:
> 
> -Reboot the VM, hit a key to interrupt Grub2 boot loader.  We need to boot
> single user (run level 1), the process for which has changed from Grub 1.
> 
> -Select your kernel, hit 'e'.
> 
> -Go down to the line starting with "linux".  Hit "End".  I needed to ignore
> the rendering bug that did not properly show the full line of text for long
> entries, just type " 1".  That is "Space" followed by "1".  Then, hit "F10".
> 
> -Your system will now boot single user and give you a command prompt.
> 
> -We need to install the VirtualBox guest additions as follows:
> 
> mount /dev/cdrom /mnt
> cd /mnt; ./VBoxLinuxAdditions.run
> reboot

VirtualBox should boot without VBoxLinuxAddition or you use nvidia drives ? 
rpmfusion have VBoxLinuxAdditions as VirtualBox-guess 
# yum install VirtualBox-guest akmod-VirtualBox  
# akmods
# systemctl restart fedora-loadmodules.service
# systemctl restart vboxservice.service

yours host system is different of Fedora ? 

and Ithink, it is not frozen, is just X that not started, if you know ( I don't) send a crtl + alt + f2 you should have a console .


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