Bug 1100942

Summary: existing OS on btrfs subvolumes to ostree fails to boot due to multiple dependency failures
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: ostreeAssignee: Colin Walters <walters>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-24 18:22:54 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
ostree-fedora-atomic-0.conf
none
journal -b -l -o short-monotonic
none
/proc/self/mountinfo
none
journal w/ systemd debug none

Description Chris Murphy 2014-05-24 05:58:37 UTC 
Description of problem: Starting with Rawhide on Btrfs installation, which uses boot, root, var, and home subvolumes, booting ostree grub entry fails to startup, ends in emergency shell due to multiple dependency failures.



Version-Release number of selected component (if applicable):
ostree-2014.4.23.gfc11c86-2.fc21.x86_64

How reproducible:
Always with the current configuration but it's a one shot with other problems seemingly with workarounds that work: bug 1100938, bug 1100940 might relate.


Steps to Reproduce:
1. Existing Rawhide installation with boot, root, var, and home subvolumes.
2. Followed this http://rpm-ostree.cloud.fedoraproject.org/#/installation
3. And the work arounds in the bugs listed above.
4. chose the grub entry ostree:fedora-atomic:0 Generic 21 (Generic), that conf file will be attached to this bug

Actual results:

Emergency target. Multiple problems. Will attach journal.


Expected results:

Successful boot.

Additional info:
Comment 1 Chris Murphy 2014-05-24 05:59:22 UTC 
Created attachment 898843 [details]
ostree-fedora-atomic-0.conf
Comment 2 Chris Murphy 2014-05-24 06:00:37 UTC 
Created attachment 898844 [details]
journal -b -l -o short-monotonic
Comment 3 Chris Murphy 2014-05-24 06:02:03 UTC 
Created attachment 898845 [details]
/proc/self/mountinfo
Comment 4 Chris Murphy 2014-05-24 06:46:28 UTC 
So it looks like systemd is mounting home and boot subvolumes on top of the ostree versions of them. When I reboot with systemd.log_level=debug, somehow it works, I don't get dropped to emergency mode. The boot and home subvols are still mounted on top of non-empty /boot and /home.
Comment 5 Chris Murphy 2014-05-24 06:47:18 UTC 
Created attachment 898857 [details]
journal w/ systemd debug
Comment 6 Chris Murphy 2014-05-24 18:22:54 UTC 
After many things, including ostree admin fsck, undeploying all trees and deploying a new one, I can't reproduce the startup failure as originally described. Also, the message that /home is not empty when mounting the home subvolume, doesn't happen. I'll close this for now.

The message that /boot is not empty, when mounting the boot subvolume, does still happen. No idea if that's a bug or expected.
Comment 7 Colin Walters 2014-05-24 19:58:27 UTC 
Interesting; I suspect there are other ostree/btrfs interaction issues.  I'm really interested in having the combination work well.  (I also want LVM to work well).

The /boot not empty is an ostree bug, I just filed it:
https://bugzilla.gnome.org/show_bug.cgi?id=730695