RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1427537 - Atomic NFS Server
Summary: Atomic NFS Server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-server-atomic
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 14:33 UTC by Marko Myllynen
Modified: 2018-04-11 00:07 UTC (History)
8 users (show)

Fixed In Version: rpm-ostree-2018.1-2.atomic.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-11 00:07:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1095 0 None None None 2018-04-11 00:07:40 UTC

Description Marko Myllynen 2017-02-28 14:33:19 UTC 
Description of problem:
This fails:

# systemctl start nfs-server.service

This works:

# touch /var/lib/nfs/etab
# systemctl start nfs-server.service

If it is not supported to run NFS server on Atomic then the related unit files should perhaps be removed. If NFS server is supported on Atomic then it should start up like on RHEL. Either way, the current situation is probably the most confusing one.

If unsupported, it would nice to document this somewhere.

Version-Release number of selected component (if applicable):
7.3.2
Comment 2 Marko Myllynen 2017-02-28 14:41:05 UTC 
Actually, on boot I also see this:

[FAILED] Failed to mount RPC Pipe File System.
See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details.
[DEPEND] Dependency failed for RPC security service for NFS client and server.
[DEPEND] Dependency failed for RPC security service for NFS server.
Comment 3 Colin Walters 2017-02-28 14:42:11 UTC 

*** This bug has been marked as a duplicate of bug 1406164 ***
Comment 4 Marko Myllynen 2017-02-28 14:50:15 UTC 
No, this is a separate issue, doing after boot:

# systemctl restart var-lib-nfs-rpc_pipefs.mount
# systemctl is-active var-lib-nfs-rpc_pipefs.mount
active
# systemctl start nfs-server.service
A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
# systemctl is-active nfs-server.service
inactive

We see:

atom.example.com rpc.mountd[11168]: couldn't open /var/lib/nfs/etab

But then:

# touch /var/lib/nfs/etab
# systemctl start nfs-server
# systemctl is-active nfs-server.service
active

Thanks.
Comment 5 Ben Breard 2017-08-25 01:34:07 UTC 
Colin,

I can verify this is still a problem w/ 7.4. This is similar to the same issue you linked to, but I think we're missing the correct tmpfile config in the nfs-utils rpm. 

This creates the necessary files, but the config file should live in the nfs-utils package and obviously be under /usr/lib/tmpfiles.d/

cat /etc/tmpfiles.d/nfs.conf 
#Type Path         Mode  UID  GID Age Argument
f     /var/lib/nfs/etab 0644  root  root  -  -
f     /var/lib/nfs/rmtab 0644  root  root  -  -
f     /var/lib/nfs/xtab 0644  root  root  -  -

Can we add something to the rpm-ostree compose to touch these files until it's added in the package?
Comment 6 Colin Walters 2018-01-15 15:25:23 UTC 
Yeah, we can work around this on the rpm-ostree side.  I may look at doing an nfs-utils patch upstream though.
Comment 7 Colin Walters 2018-02-05 16:07:39 UTC 
Things appear to work in Fedora 27 Atomic Host; there's been a lot of changes in upstream nfs-utils in this area.  I didn't fully try to analyze all of them, but I am guessing it's http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=8e98eed42b64aa388c09716e3276a53028a839bf that made things work here.

I think though it's not going to hurt to just always add the etab/mtab to our tmpfiles.d set in rpm-ostree.
Comment 8 Colin Walters 2018-02-05 18:17:16 UTC 
https://github.com/projectatomic/rpm-ostree/pull/1229
Comment 12 errata-xmlrpc 2018-04-11 00:07:33 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-2018:1095
Note You need to log in before you can comment on or make changes to this bug.