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.

Bug 2036550

Summary: ypbind fails to start if kernel cmdline has ipv6.disable=1
Product: Red Hat Enterprise Linux 8 Reporter: Vaclav Danek <vdanek>
Component: ypbindAssignee: Ondřej Sloup <osloup>
Status: CLOSED WONTFIX QA Contact: Vaclav Danek <vdanek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.5CC: databases-maint, hhorak, jkejda, mmuzila
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: mkulik: needinfo+
pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-03 07:28:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vaclav Danek 2022-01-03 02:47:08 UTC
Description of problem:
ypbind fails to start if kernel cmdline has ipv6.disable=1

Version-Release number of selected component (if applicable):
ypbind-2.5-2.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. steps from https://bugzilla.redhat.com/show_bug.cgi?id=1974925#c7
2. add ipv6.disable to slave too

Actual results:
Jan 02 21:33:56 localhost ypbind[2722]: Cannot create socket for inet6,udp: Address family not supported by protocol
Jan 02 21:33:56 localhost ypbind[2722]: Cannot create socket for inet6,tcp: Address family not supported by protocol
Jan 02 21:33:56 localhost ypbind[2727]: Binding NIS service
Jan 02 21:34:00 localhost ypserv[2520]: refuse to transfer map from 10.19.241.47807, no valid domain
Jan 02 21:34:43 localhost ypbind[2782]: Binding took 47 seconds
Jan 02 21:34:43 localhost ypbind[2784]: NIS server for domain example.com is not responding.
Jan 02 21:34:43 localhost ypbind[2785]: Killing ypbind with PID 2722.
Jan 02 21:34:43 localhost ypbind[2786]: Try increase NISTIMEOUT in /etc/sysconfig/ypbind

Expected results:
ypbind starts

Comment 5 RHEL Program Management 2023-07-03 07:28:22 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 6 Red Hat Bugzilla 2023-11-01 04:25:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days