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 2207801 - amd map format netgoup selector function not working
Summary: amd map format netgoup selector function not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: autofs
Version: 8.7
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ian Kent
QA Contact: Kun Wang
URL:
Whiteboard:
Depends On:
Blocks: 2210899
TreeView+ depends on / blocked
 
Reported: 2023-05-16 23:40 UTC by Ian Kent
Modified: 2023-11-14 18:01 UTC (History)
6 users (show)

Fixed In Version: autofs-5.1.4-105.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2210899 (view as bug list)
Environment:
Last Closed: 2023-11-14 15:48:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-157431 0 None None None 2023-05-16 23:41:14 UTC
Red Hat Product Errata RHBA-2023:7098 0 None None None 2023-11-14 15:48:55 UTC

Description Ian Kent 2023-05-16 23:40:33 UTC
Description of problem:

Jonathan from Morgan has been continuing testing with the RHEL8 autofs, and the earlier issues with the hangs and the like are gone (Thanks again for that). He did have a pair of questions around netgrp handling and selectors if you have a moment:

<customer email>

We have hit another snag with the AMD compatibility layer in AutoFS. Can you kindly reach out to Ian and find out if the netgrpd() functionality was ported in to AutoFS AMD compatibility layer?

We have several escalations of mount failures due to the following:

May  2 17:16:18 [REDACTED HOSTNAME] automount[2410]: parse_mount: parse(amd): failed to parse entry: netgrpd(aveksa_hosts_all_nonprod);addopts:=sec=sys;rhost:=[REDACTED];rfs:=[REDACTED] || addopts:=sec=krb5,vers=4;rhost:=[REDACTED];rfs:=[REDACTED]

There are a little over 3000 shares in the plant relying on the netgrpd() functionality so this is causing some pain.

The netgrpd() functionality AND selectors (‘||’). The time we use selectors is when we have a group of hosts that needs to mount the share with a different security_flavor than the default.

Version-Release number of selected component (if applicable):
autofs-5.1.4-103.el8

How reproducible:
Always

Steps to Reproduce:
1.
1a) add "/test	file,amd:/etc/amd.test" to /etc/auto.master.
1b) create /etc/amd.test as
mnt1    netgrpd(mynetgroupd);type:=nfs;rhost:=centos7;rfs:=/autofs/export1 || type:=nfs;rhost:=centos7;rfs:=/autofs/export2
mnt2    netgrpd(othernetgroupd);type:=nfs;rhost:=centos7;rfs:=/autofs/export1 netgrpd(mynetgroupd);type:=nfs;rhost:=centos7;rfs:=/autofs/export2

2. Create /etc/netgroup as
mynetgroup	(donald,,themaw.net)(gandalf,,themaw.net)
mynetgroupd	(donald.themaw.net,,themaw.net)(gandalf.themaw.net,,themaw.net)

3. Start autofs, ensure /test gets mounted and try "ls /test/mnt1" or
   "ls /test/mnt2"
4. Observe the "failed to parse entry" entry in the systemd journal.

This assumes an NFS server named centos7.themaw.net that has exported
directories of /autofs/export1 and /autofs/export2, and an autofs
client named donald.themaw.net setup as above.

Actual results:
The mount fails with a parse error.

Expected results:
No parse error is seen and the appropriate mount is attempted,
either for a netgroup name match orthe one corresponding to not
a match.

Comment 3 Ian Kent 2023-05-17 00:09:03 UTC
Resolving these recently discovered bugs with the autofs amd map format
support is important to providing an alternative to the am-utils package
that's not available in RHEL.

With resolving this problem I hope there won't be further show stopper
problems so that this is the last important, time critical fix that we
need to provide.

Since this is an important fix I'm recommending we cancel the hot fix
we were going to provide from bug 2175017/2192275 and use the package
from this bug.

Is this ok, FrankH, FrankS, DaveW?

Ian

Comment 4 Ian Kent 2023-05-17 00:11:39 UTC
There were a few other problems mentioned in an initial email, once
we've sorted this problem out I'd like to review what we still have
to do and the priorities.

Comment 14 errata-xmlrpc 2023-11-14 15:48:36 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-2023:7098


Note You need to log in before you can comment on or make changes to this bug.