Bug 1352005

Summary:	IPV6 addresses assigned inconsistently to device configured with ipv4 only via dracut options (static vs dhcp method)
Product:	Red Hat Enterprise Linux 7	Reporter:	Radek Vykydal <rvykydal>
Component:	dracut	Assignee:	Lukáš Nykrýn <lnykryn>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dracut-maint-list, harald, lnykryn, sbueno
Target Milestone:	rc
Target Release:	---
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:	2020-12-15 07:42:43 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:
Bug Depends On:
Bug Blocks:	1309661

Description Radek Vykydal 2016-07-01 11:36:03 UTC

(Observed in installer) When configuring a device with ipv4 only with dracut options the device has ipv6 addresses autoconfigured if ipv4 is configured with dhcp, eg "ip=ens3:dhcp", while it has no ipv6 address [1] if ipv4 is configured statically, eg "ip=10.34.102.40::10.34.102.254:255.255.255.0::ens3:none"

[1] addresses autoconfigured by kernel are flushed in modules.d/40network/ifup.sh:do_static()

This inconsistency poses problem for taking over ibft (dhcp vs static ipv4) connections by NM after switchroot -> bug 1309661.

Comment 2 Radek Vykydal 2017-01-18 13:28:35 UTC

Are you considering fixing this in RHEL 7.4?

Comment 6 RHEL Program Management 2020-12-15 07:42:43 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.