Bug 1542604

Summary:	[RFE] HE setup: Ansible Flow: Show only active network interfaces for setting ovirtmgmt bridge
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Ido Rosenzwig <irosenzw>
Component:	Network	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2.0	CC:	bugs, stirabos, trichard
Target Milestone:	ovirt-4.2.2	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	rule-engine: ovirt-4.2? sbonazzo: exception? nsednev: testing_plan_complete+ rule-engine: planning_ack? sbonazzo: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-setup-2.2.10	Doc Type:	Enhancement
Doc Text:	Self-hosted engine installation using Ansible now only shows active network interfaces for setting the ovirtmgmt bridge.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:07:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1458709

Description Ido Rosenzwig 2018-02-06 16:10:00 UTC

Description of problem:
Show only active network interfaces for setting ovirtmgmt bridge  


Steps to Reproduce:
1. have disabled NIC
2. run hosted-engine --deploy --ansible
3. see the NIC can be chosen for setting ovirtmgmt bridge

Comment 1 Nikolai Sednev 2018-02-14 20:24:28 UTC

Works for me on these components:
rhvm-appliance-4.2-20180202.0.el7.noarch
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch
Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
During deployment I've seen only active interfaces.

Comment 2 Sandro Bonazzola 2018-03-29 11:07:58 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

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