Bug 1829682

Summary: Unable to boot silverblue on btrfs encrypted with luks2
Product: [Fedora] Fedora Reporter: Junjie Yuan <yuan>
Component: anacondaAssignee: Colin Walters <walters>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 32CC: anaconda-maint-list, dustymabe, jkonecny, jlebon, jonathan, jonathan, kellin, miabbott, vanmeeuwen+fedora, vponcova, walters, wwoods
Target Milestone: ---Keywords: Desktop
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: 2020-08-01 12:17:37 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
Startup Information
none
Startup Information in host machine
none
initramfs rdsosreport
none
journalctl -b none

Description Junjie Yuan 2020-04-30 05:22:34 UTC 
Created attachment 1683194 [details]
Startup Information

Description of problem:
failed to start OSTree Prepare OS / causes Fedora Silverblue 32 to fail to start

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


How reproducible:


Steps to Reproduce:
1. Install Fedora Silverblue 32
2. boot
3.

Actual results:
The service failed to start, causing the service to restart and fail to start the system.

Expected results:
System startup

Additional info:
ISO: https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-32-1.6.iso
Comment 1 Junjie Yuan 2020-04-30 05:29:22 UTC 
The file system is Btrfs, which is automatically set by the one-click creation function of the fedora installer.

Please check the attached picture, there is a line of gray logs:

There is no file or directory "/sysroot//ostree......". Could the double slash cause this problem?
Comment 2 Jonathan Lebon 2020-04-30 18:27:27 UTC 
Hmm, we used to have btrfs issues in the past, though it apparently fixed itself in f31 (see https://bugzilla.redhat.com/show_bug.cgi?id=1289752). I haven't really played with btrfs much; what is the default layout Anaconda applied?
Comment 3 Junjie Yuan 2020-05-11 07:27:22 UTC 
Created attachment 1687171 [details]
Startup Information in host machine
Comment 4 Junjie Yuan 2020-05-11 07:32:23 UTC 
I'm sorry to reply so late.

Please check the attachment, I think these two issues are not the same.

The following is the partition layout created by anaconda with one click (by default, luks encryption is not used)

/sda1 ESP
/sda2 /boot
/sda3 swap
/sda4 btrfs partition over luks2 ------ subvolumes root and home
Comment 5 Junjie Yuan 2020-07-10 04:22:16 UTC 
Created attachment 1700526 [details]
initramfs rdsosreport
Comment 6 Junjie Yuan 2020-07-10 04:22:43 UTC 
Created attachment 1700527 [details]
journalctl -b
Comment 7 Junjie Yuan 2020-07-10 04:24:48 UTC 
This issue can be reproduced in the latest Rawhide.

ISO: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20200607.n.0.iso
Comment 8 Jonathan Lebon 2020-07-10 13:30:43 UTC 
I think this is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1753485. Will let the Anaconda team confirm and close it out if they agree.
Comment 9 Junjie Yuan 2020-08-01 12:17:37 UTC 
Fixed in Fedora-Silverblue-ostree-x86_64-Rawhide-20200731.n.0.iso

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