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 1958485 - autofs amd type host mounts fail for certain host names
Summary: autofs amd type host mounts fail for certain host names
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: autofs
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: beta
: 8.5
Assignee: Ian Kent
QA Contact: Kun Wang
URL:
Whiteboard:
: 1961523 (view as bug list)
Depends On:
Blocks: 1958486
TreeView+ depends on / blocked
 
Reported: 2021-05-08 07:30 UTC by Ian Kent
Modified: 2021-11-10 07:15 UTC (History)
2 users (show)

Fixed In Version: autofs-5.1.4-68.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1958486 (view as bug list)
Environment:
Last Closed: 2021-11-09 19:32:44 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch - fix amd hosts mount expire (1.63 KB, patch)
2021-05-10 00:30 UTC, Ian Kent 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4372 0 None None None 2021-11-09 19:32:58 UTC

Description Ian Kent 2021-05-08 07:30:38 UTC 
Description of problem:
autofs amd mounts that are present in the autofs configuration, rather than in the master map itself, are umounted when the automount configuration is reloaded.

Not sure when this started happening. 

How reproducible:
always.


Steps to Reproduce:
1. Add an amd entry to /etc/autofs.conf
   eg., at the bottom of /etc/autofs.conf add:

[ /test/redhat ]
# map name must be defined, all else are optional
map_name = amd.redhat

Where /etc/amd.redhat contains, say:
exports   fs:=${map};pref:=${key}
exports/* hostd==${/key}.long.domain.name.themaw.net;type:=link;fs:=/ \
          hostd!=${/key}.long.domain.name.themaw.net; \
            type:=host; rhost:=${/key}.long.domain.name.themaw.net;\
            opts:=rw,hard,intr,nosuid,retrans=9,timeo=45;\
            fs:=${autodir}/redhat/${key}

You might need to get rid of the line continueations following the
hostd!=...
2. Setup an nfs server, the one here is f28.long.domain.name.themaw.net
   and export some paths, for example /raven, /exports, etc.
3. Start NFS on the server and ensure clients an mount its exports.
4  Now, on the client start autofs and try and access one of the exports
   with:
   ls /test/redhat/exports/f28/exports/raven

Actual results:
The export fails to mount.

Expected results:
The export mounts and is accessable.

Additional info:
This is the same failure I have been seeing in the CI test amd-basic,
the last test always failing.

I had been unable to reproduce it and running the test manually on
beaker would always succeed which I couldn't understand since the 
tests themselves look fine.

Hopefully this will resolve my CI problem at last.
Comment 1 Ian Kent 2021-05-08 07:36:22 UTC 
(In reply to Ian Kent from comment #0)
> Description of problem:
> autofs amd mounts that are present in the autofs configuration, rather than
> in the master map itself, are umounted when the automount configuration is
> reloaded.

The reproducer actually describes and mount type host failing for an unknown
reason.

It seems to be longer host names that are a problem.
Comment 2 Ian Kent 2021-05-08 07:46:56 UTC 
(In reply to Ian Kent from comment #0)
> 
> Steps to Reproduce:
> 1. Add an amd entry to /etc/autofs.conf
>    eg., at the bottom of /etc/autofs.conf add:
> 
> [ /test/redhat ]
> # map name must be defined, all else are optional
> map_name = amd.redhat
> 
> Where /etc/amd.redhat contains, say:
> exports   fs:=${map};pref:=${key}
> exports/* hostd==${/key}.long.domain.name.themaw.net;type:=link;fs:=/ \
>           hostd!=${/key}.long.domain.name.themaw.net; \
>             type:=host; rhost:=${/key}.long.domain.name.themaw.net;\
>             opts:=rw,hard,intr,nosuid,retrans=9,timeo=45;\
>             fs:=${autodir}/redhat/${key}
> 
> You might need to get rid of the line continueations following the
> hostd!=...
> 2. Setup an nfs server, the one here is f28.long.domain.name.themaw.net
>    and export some paths, for example /raven, /exports, etc.
> 3. Start NFS on the server and ensure clients an mount its exports.
> 4  Now, on the client start autofs and try and access one of the exports
>    with:
>    ls /test/redhat/exports/f28/exports/raven
> 
> Actual results:
> The export fails to mount.
> 
> Expected results:
> The export mounts and is accessable.
> 
> Additional info:
> This is the same failure I have been seeing in the CI test amd-basic,
> the last test always failing.
> 
> I had been unable to reproduce it and running the test manually on
> beaker would always succeed which I couldn't understand since the 
> tests themselves look fine.
> 
> Hopefully this will resolve my CI problem at last.

You might be able to reproduce this with the amd-basic Beaker test
but as I say it always worked when I ran it manually.
Comment 3 Ian Kent 2021-05-10 00:30:51 UTC 
Created attachment 1781461 [details]
Patch - fix amd hosts mount expire
Comment 6 Ian Kent 2021-05-19 00:59:25 UTC 
*** Bug 1961523 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2021-11-09 19:32:44 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 (autofs bug fix and enhancement update), 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-2021:4372
Note You need to log in before you can comment on or make changes to this bug.