Bug 1404210

Summary:	Anaconda creates wrong dracut boot options and ifcfg files for 2 NICs (ibft + non-ibft) if they share L3 subnet.
Product:	Red Hat Enterprise Linux 6	Reporter:	Radek Vykydal <rvykydal>
Component:	anaconda	Assignee:	Radek Vykydal <rvykydal>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.8
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:	2017-12-06 10:57:37 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:

Description Radek Vykydal 2016-12-13 11:15:41 UTC

Based on https://bugzilla.redhat.com/show_bug.cgi?id=1396949#c14

Anaconda sets incorrect dracut boot option ip= and incorrect ifcfg file values for NM_CONTROLLED.

The use case is: 
Two devices in the same subnet: <PXE> device, <IBFT> device.
(I'd expect <IBFT> device on separate subnet in most cases though)

<IBFT> device and target is configured in iBFT.

Boot option: ksdevice=bootif (ie booting from PXE with ipappend=2 PXE command supplying BOOTIF boot option)
-> the <PXE> device is activated by anaconda (loader) based on ksdevice=bootif
-> the <IBFT> device is activated by NM by iBFT plugin [2]

<PXE> device gets the default route, and as both devices are on the same subnet, the iSCSI target is accessed via the <PXE> device in installer environment (as it is on the same subnet).

Anaconda when examining iSCSI devices containing root fs (ie those that need the network device to be activated in initramfs) configured from iBFT configures 1) for the device used to access the LUN NM_CONTROLLED value to "no" and 2) dracut boot options (ip=, ifname=).

In this case it finds out (via route command) that the device is <PXE>, which results in:

- NM_CONTROLLED=no in ifcfg-<PXE> file
- NM_CONTROLLED=yes in ifcfg-<IBFT> file
- ifname=<PXE>:<MAC>
- ip=<PXE>:<PXE configuration from its ifcfg file>

but the correct settings shuld be

- NM_CONTROLLED=no in ifcfg-<IBFT> file
- NM_CONTROLLED=yes in ifcfg-<PXE> file
- ifname=<IBFT>:<MAC> [1]
- ip=ibft

Comment 3 Radek Vykydal 2016-12-15 12:20:17 UTC

https://github.com/rhinstaller/anaconda/pull/907

Comment 5 Jan Kurik 2017-12-06 10:57:37 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/