Bug 1375388

Summary: [LLNL 7.4 FEAT] RFE don't require /etc/fstab for kdumpctl
Product: Red Hat Enterprise Linux 7 Reporter: Ben Woodard <woodard>
Component: kexec-toolsAssignee: Pratyush Anand <panand>
Status: CLOSED ERRATA QA Contact: Qiao Zhao <qzhao>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: cye, foraker1, panand, piliu, ruyang, silva50, tgummels, woodard
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kexec-tools-2.0.7-52.el7.src.rpm Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:31:21 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:
Bug Depends On:    
Bug Blocks: 1289208, 1384121, 1384257, 1394638, 1404314, 1446211    

Description Ben Woodard 2016-09-13 00:57:15 UTC
Description of problem:

kdumpctl requires the presence of /etc/fstab or else the service fails to start.
Our diskless clients do not have /etc/fstab and they work perfectly well. To make kdump start we have to make an empty /etc/fstab and set its date to something sufficiently old that making a new initramrd doesn't get built. This is inconvenient. We think that if /etc/fstab were actually truly needed then having an empty file would not be sufficient. The fact that it works so long as the file exists even if it is empty suggests that it isn't really needed. Therefore, we think that the kexec tools should not error out if there is no /etc/fstab.

An /etc/fstab wasn't needed in rhel6

Comment 2 Pratyush Anand 2016-09-14 14:44:45 UTC
Posted patch to the upstream(kexec.org) for review. It will be back ported to rhel7 after upstream review and merging.

Comment 9 errata-xmlrpc 2017-08-01 09:31:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2300