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.
+++ This bug was initially created as a clone of Bug #1958485 +++
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.
--- Additional comment from Ian Kent on 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.
--- Additional comment from Ian Kent on 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.