Red Hat Bugzilla – Bug 884696
fedup backtrace on F17 EFI live install: 'error opening /boot/grub/grub.cfg for read: no such file or directory'
Last modified: 2013-01-03 02:25:59 EST
I attempted to upgrade an updated F17 EFI live install using fedup-0.7.2-0.fc17 and it failed on 'grubby --default-kernel'. Running the command manually, I see the following output: error opening /boot/grub/grub.cfg for read: no such file or directory Debug logs to follow shortly
Created attachment 658811 [details] debug log from fedup prep attempt Attaching the debug log from my upgrade attempt. Command used: sudo fedup-cli --network 18 --debuglog=fedupdebug.log --instrepo=http://dl.fedoraproject.org/pub/fedora/linux/releases/test/18-Beta/Fedora/x86_64/os/
Tried again with fedup-0.7.2-0.git20121206.fc17 and the upgrade completed as expected. Doesn't upgrade the kernel but that's not really a fedup issue
fedup-0.7.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.2-1.fc17
Package fedup-0.7.2-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.7.2-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20801/fedup-0.7.2-1.fc17 then log in and leave karma (feedback).
fedup-0.7.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.