This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2098193 - autofs should not start rpc-statd and rpcbind
Summary: autofs should not start rpc-statd and rpcbind
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: autofs
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ian Kent
QA Contact: Kun Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-17 14:23 UTC by Orion Poplawski
Modified: 2024-01-22 04:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 11:07:59 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   RHEL-7880 0 None Migrated None 2023-09-23 11:07:53 UTC
Red Hat Issue Tracker RHELPLAN-125608 0 None None None 2022-06-17 14:44:14 UTC

Description Orion Poplawski 2022-06-17 14:23:59 UTC 
Description of problem:

We use NFSv4 mounts only and so do not need rpc-statd or rpcbind, but starting autofs starts them presumably due to:

Wants=network-online.target rpc-statd.service rpcbind.service

Version-Release number of selected component (if applicable):
autofs-5.1.4-82.el8.x86_64
Comment 1 Orion Poplawski 2022-06-17 14:27:38 UTC 
Actually, maybe it's the After= line, which seems odd.  I've removed the Wants entries and that did seem to help.
Comment 2 Orion Poplawski 2022-06-17 14:52:37 UTC 
Sorry, I was failing to properly remove the Wants= (can't use autofs.service.d/override.conf to remove Wants=).
Comment 3 Ian Kent 2022-06-18 01:22:13 UTC 
(In reply to Orion Poplawski from comment #0)
> Description of problem:
> 
> We use NFSv4 mounts only and so do not need rpc-statd or rpcbind, but
> starting autofs starts them presumably due to:
> 
> Wants=network-online.target rpc-statd.service rpcbind.service
> 
> Version-Release number of selected component (if applicable):
> autofs-5.1.4-82.el8.x86_64

What problems does this cause?

There were some odd problems that lead to adding some of those entries,
I'll need to check why.

And be aware I'm going to be out of action for a while so there will
be a delay in me getting back to you, sorry.

Ian
Comment 4 Ian Kent 2022-06-20 08:38:23 UTC 
(In reply to Orion Poplawski from comment #0)
> Description of problem:
> 
> We use NFSv4 mounts only and so do not need rpc-statd or rpcbind, but
> starting autofs starts them presumably due to:

There were some problems recently.

You know that, if you want to use NFSv4 without autofs trying to
contact rbcbind, you need to disable fallback to other NFS protocol
versions in your map entries.

That needs to be done by using the fstype option and setting it
to nfs4.
Comment 5 Ian Kent 2022-07-05 03:54:47 UTC 
(In reply to Ian Kent from comment #4)
> (In reply to Orion Poplawski from comment #0)
> > Description of problem:
> > 
> > We use NFSv4 mounts only and so do not need rpc-statd or rpcbind, but
> > starting autofs starts them presumably due to:
> 
> There were some problems recently.
> 
> You know that, if you want to use NFSv4 without autofs trying to
> contact rbcbind, you need to disable fallback to other NFS protocol
> versions in your map entries.
> 
> That needs to be done by using the fstype option and setting it
> to nfs4.

Did you give this some thought?
If specifying the option "fstype=nfs4" doesn't work properly then I'll
need to fix it. 

I'm concerned about breaking other things that have been fixed by just
removing those dependencies.
Comment 6 RHEL Program Management 2023-09-23 11:06:38 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-23 11:07:59 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 8 Red Hat Bugzilla 2024-01-22 04:25:17 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.