Bug 1416687

Summary:	--activate and --onboot kickstart network options not honored for bridge configured in kickstart
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:	jstodola, pkotvan, sbueno
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-21.48.22.95-1	Doc Type:	No Doc Update
Doc Text:	undefined	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 2017-01-26 09:14:23 UTC

Description of problem:

--activate and --onboot options are not honored when configuring bridge devices in kickstart

Version-Release number of selected component (if applicable):

RHEL 7.3
anaconda-21.48.22.93-1

How reproducible:

Always

Steps to Reproduce:

Run installation (eg in kvm with 2 network devices) with ip=ens3:dhcp network boot option and the kickstart network configuration:

network --device=bridge0  --bridgeslaves=ens3 --bootproto=dhcp --onboot=no
network --device=bridge1  --bridgeslaves=ens4 --bootproto=dhcp

Actual results:

bridge1 is activated in installer
slave of bridge0 has ONBOOT=yes set in ifcfg file (ifcfg-bridge0_slave1)

Expected results:

bridge1 is not activated in installer (because no --activate option is set)
slave of bridge0 has ONBOOT=no set in ifcfg file (ifcfg-bridge0_slave1)

Additional info:

Comment 1 Radek Vykydal 2017-01-26 10:11:53 UTC

https://github.com/rhinstaller/anaconda/pull/939
Depends on
https://github.com/rhinstaller/anaconda/pull/938/commits/4458d7c7a2171a8b97aa895c8a3f332179a76554
for bug 1416655.

Comment 4 Peter Kotvan 2017-05-09 12:43:04 UTC

Verified on RHEL-7.4-20170504.0 with anaconda-21.48.22.111-1.el7. Thanks.

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