Bug 1784690

Summary: netinst rescue backtrace if installed /etc/fstab has tmpfs mount - no attribute _chrooted_mountpoint
Product: [Fedora] Fedora Reporter: Chris Schanzle <bugzilla>
Component: python-blivetAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: anaconda-maint-list, blivet-maint-list, dlehman, jkonecny, jonathan, kellin, mkolman, rvykydal, vanmeeuwen+fedora, vponcova, vtrefny, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-blivet-3.2.0-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-15 12:13:55 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
storage.log
none
program.log
none
dbus.log
none
anaconda.log
none
screenshot of backtrace none

Description Chris Schanzle 2019-12-18 05:42:51 UTC
Description of problem:
boot 'rescue' via usb Fedora-Server-netinst-x86_64-31-1.9.iso with tmpfs in installed system's /etc/fstab results in backtrace.


Version-Release number of selected component (if applicable):
Fedora-Server-netinst-x86_64-31-1.9.iso

How reproducible:
always

Steps to Reproduce:
1. in an installed system's /etc/fstab, create a tmpfs mount:

swap /home/schanzle/.cache  tmpfs  size=512m,uid=schanzle,gid=19249,mode=700,nodev,nosuid 0 0

2.  Boot the netinst image selecting the rescue option
3.  select to mount read-write

Actual results:
Python traceback with:
AttributeError: 'TmpFS' object has no attribute '_chrooted_mountpoint'

Expected results:
mounted filesystems

Additional info:
commenting out the fstab entry enables rescue to mount the filesystems.
shouldn't be significant, but my /home filesystem is Luks.  Happy to test on another system if needed.

Happy to attach full traceback upon request.  I have a (good) photo of the screen I could attach here.  Please teach me how to find the traceback in a log or otherwise save it.

Comment 1 Vendula Poncova 2019-12-18 10:40:04 UTC
Please, attach all logs from the rescue. You can find them in /tmp/*log.

Comment 2 Chris Schanzle 2019-12-18 17:39:33 UTC
Created attachment 1646138 [details]
storage.log

Comment 3 Chris Schanzle 2019-12-18 17:40:00 UTC
Created attachment 1646139 [details]
program.log

Comment 4 Chris Schanzle 2019-12-18 17:40:42 UTC
Created attachment 1646140 [details]
dbus.log

Comment 5 Chris Schanzle 2019-12-18 17:41:16 UTC
Created attachment 1646141 [details]
anaconda.log

Comment 6 Chris Schanzle 2019-12-18 17:42:27 UTC
Created attachment 1646142 [details]
screenshot of backtrace

I searched the logs for the backtrace and didn't find it, so here's a screenshot.

Comment 7 Chris Schanzle 2019-12-18 17:49:58 UTC
sensitive-info.log and packaging.log were empty, so not attached.  Thanks!

Comment 8 Jiri Konecny 2020-01-02 14:19:55 UTC
This error is raised from our storage library. Switching component.

Comment 9 Vojtech Trefny 2020-01-02 15:02:44 UTC
upstream PR: https://github.com/storaged-project/blivet/pull/822