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:	ypbind	Assignee:	Ondřej Sloup <osloup>
Status:	CLOSED WONTFIX	QA Contact:	Vaclav Danek <vdanek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	databases-maint, hhorak, jkejda, mmuzila
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	mkulik: needinfo+ mkulik: needinfo? (vdanek)
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.