Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
A systemd automount with the option 'x-systemd.automount' that times out will not end up in a failed state and it keeps trying to mount NFS file system in BG and will never fail.

Version-Release number of selected component (if applicable):
systemd-219-57.el7.x86_64


Steps to Reproduce:
1. Add following in NFS mount entry in etc/fstab

# fgrep noauto /etc/fstab 
192.168.100.x:/data	/mnt			nfs	noauto,x-systemd.automount    0 0

2. Stop NFS service on the server 

3. Execute 'cd /mnt'. At this point the shell hangs waiting for reply

# journalctl -u mnt.mount 
Mar 26 02:21:56 localhost.localdomain systemd[1]: Mounting /mnt...
Mar 26 02:23:26 localhost.localdomain systemd[1]: mnt.mount mounting timed out. Stopping.
Mar 26 02:23:26 localhost.localdomain systemd[1]: Mounted /mnt.

# journalctl -u mnt.automount
Mar 26 02:21:56 localhost.localdomain systemd[1]: Got automount request for /mnt, triggered by 2366 (bash)
Mar 26 02:23:26 localhost.localdomain systemd[1]: Got automount request for /mnt, triggered by 2366 (bash)

It has been 10 mins now and my Shell prompt still hung and don't exit. 

[root@localhost ~]# cd /mnt


Additional info:

https://github.com/systemd/systemd/issues/4055
https://github.com/systemd/systemd/issues/7038
https://github.com/systemd/systemd/issues/4275

This seems to be fixed in upstream, we are currently looking into its backportability.

PR: https://github.com/systemd-rhel/rhel-7/pull/36

fix merged to github master branch -> https://github.com/systemd-rhel/rhel-7/pull/36 -> post

*** Bug 1672228 has been marked as a duplicate of this bug. ***

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-2020:1117