Bug 1113156

Summary: Empty fstab breaks libguestfs inspection
Product: [Community] Virtualization Tools Reporter: Richard W.M. Jones <rjones>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, mbooth, ptoscano
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-07-07 12:00:48 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:

Description Richard W.M. Jones 2014-06-25 14:09:54 UTC
Description of problem:

Systemd allows an empty /etc/fstab, if every mountpoint uses a
systemd unit (see bug 1113153).  I believe (though I haven't tested
it) that if there is only a root filesystem, then /etc/fstab can
also be empty and at least systemd won't mind, although I imagine
lots of other software wouldn't be too happy.

If /etc/fstab exists but is empty then you get:

libguestfs: could not parse /etc/fstab or empty file

We should not fail in this case.

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

libguestfs 1.27.19

Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=1113153
https://bugs.launchpad.net/nova/+bug/1221985

Comment 1 Pino Toscano 2014-07-07 12:00:48 UTC
Fixed with
https://github.com/libguestfs/libguestfs/commit/3fc6983b1666a32ea6c1b44d88f140e3c84e7201
which is libguestfs >= 1.27.21.