Bug 1635514

Summary: Silverblue failed to continue installation after failing to install the boot loader
Product: [Fedora] Fedora Reporter: Paul Dufresne <dufresnep>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 29CC: anaconda-maint-list, butirsky, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, walters, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-04 10:38:09 UTC Type: Bug
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 log
none
blivet-gui-utils
none
program log
none
storage log
none
storage state
none
storage state none

Description Paul Dufresne 2018-10-03 07:02:32 UTC
Was installing from Fedora-Silverblue-ostree-x86_64-29_Beta-1.5.iso written and 
verified on an USB key.

I choose a manual installation because my disk had about the following:
part1 Haiku-beta
part2 Ubuntu 18.10 beta mate 
part3 Fedora28
part4 swap

So I chosen to erase part3, and recreate a new ext4 on / for Fedo 29.

Things seems to go well, until system said it was not able to
install boot loader.

Then I had to choose between abandon, and continue, I choosed continue.

Then I received a fatal error had happened with following info:

ostree ['admin','instutil','set-kargs','resume=UUID=3ed5af1e-e215-4441-a764-927d8cf3ae59','rhgb','quiet','root-UUID-bef3be1d-d5e3-4923-bf8f-
a87d4be274a0'] exited with code 1

So I was force to stop installation.

I then tried in ubuntu, update-grub, but Fedora was not listed in detected systems.

Comment 1 Paul Dufresne 2018-10-03 07:38:16 UTC
The first time, I was not aware that log files were in /tmp.
I have redone an installation, with very similar results and I intend to attach
the files to this bug.

But I not at the end of program.log:
02:21:15,044 INF program: Running in chroot '/mnt/sysimage/ostree/deploy/fedora-workstation/deploy/d5b60890b8c319c87622575fe6d31bf32fd4a135949c81e6ce98481b8ece9c6f.0'... grub2-mkconfig -o /boot/grub2/grub.cfg
02:21:18,100 INF program: /usr/bin/grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or directory.
02:21:18,101 INF program: /sbin/grub2-mkconfig: line 268: /boot/grub2/grub.cfg.new: No such file or directory
02:21:18,104 DBG program: Return code: 1
02:24:12,550 INF program: Running in chroot '/mnt/sysimage/ostree/deploy/fedora-workstation/deploy/d5b60890b8c319c87622575fe6d31bf32fd4a135949c81e6ce98481b8ece9c6f.0'... ostree admin instutil set-kargs resume=UUID=3ed5af1e-e215-4441-a764-927d8cf3ae59 rhgb quiet root=UUID=77798e37-6ef8-4164-b7ff-643b97b54b21
02:24:13,825 INF program: error: Unable to find a deployment in sysroot
02:24:13,827 DBG program: Return code: 1

where it seems to create grub.cfg, but searching fior grub.cfg.new

Comment 2 Paul Dufresne 2018-10-03 07:39:15 UTC
Created attachment 1489815 [details]
anaconda log

Comment 3 Paul Dufresne 2018-10-03 07:40:12 UTC
Created attachment 1489816 [details]
blivet-gui-utils

Comment 4 Paul Dufresne 2018-10-03 07:42:40 UTC
Created attachment 1489817 [details]
program log

Comment 5 Paul Dufresne 2018-10-03 07:43:24 UTC
Created attachment 1489818 [details]
storage log

Comment 6 Paul Dufresne 2018-10-03 07:50:00 UTC
Created attachment 1489829 [details]
storage state

Comment 7 Paul Dufresne 2018-10-03 07:50:51 UTC
Created attachment 1489834 [details]
storage state

Comment 8 Jiri Konecny 2018-10-03 09:29:14 UTC
This could be some problem between partitioning, ostree and grub2. 

Colin could you please take a look on this if this is something ostree related?

Comment 9 Jiri Konecny 2018-10-03 09:32:00 UTC
We are getting this error on Live DVD when we running out of space. Maybe this could be similar issue?

Comment 10 Colin Walters 2018-10-03 13:01:14 UTC
Likely a dup of https://bugzilla.redhat.com/show_bug.cgi?id=1575957
Though it's a different symptom here.
TL;DR: ostree isn't yet ready to handle preserving an existing /boot

Comment 11 Jiri Konecny 2018-10-04 10:38:09 UTC
Thanks for info Colin,

Closing this bug. If the issues will persist after the bug 1575957 will be solved please feel free to reopen this bug again.

*** This bug has been marked as a duplicate of bug 1575957 ***