Bug 1401403

Summary:	Team slave ifcfg files are indexed starting from 0.
Product:	Red Hat Enterprise Linux 7	Reporter:	Radek Vykydal <rvykydal>
Component:	anaconda	Assignee:	Radek Vykydal <rvykydal>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	jikortus, jstodola, sbueno
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-21.48.22.96-1	Doc Type:	No Doc Update
Doc Text:	If this bug requires documentation, please select an appropriate Doc Type value.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 08:53:21 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 Radek Vykydal 2016-12-05 07:25:09 UTC

Team slave ifcfg files are indexed starting from 0, ie team0_slave_0.
We should make this consistent with bonding and also with NetworkManager naming which starts with 1.

Master fix:
https://github.com/rhinstaller/anaconda/commit/a74d80ddd0d04e825075508d8ec2c10d0aa8981e

Comment 2 Radek Vykydal 2017-02-02 09:51:43 UTC

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

Comment 5 errata-xmlrpc 2017-08-01 08:53:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2293