Bug 1542604 - [RFE] HE setup: Ansible Flow: Show only active network interfaces for setting ovirtmgmt bridge
Summary: [RFE] HE setup: Ansible Flow: Show only active network interfaces for setting...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: Network
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.2.2
: ---
Assignee: Ido Rosenzwig
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks: 1458709
TreeView+ depends on / blocked
 
Reported: 2018-02-06 16:10 UTC by Ido Rosenzwig
Modified: 2018-05-17 12:29 UTC (History)
3 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.2.10
Clone Of:
Environment:
Last Closed: 2018-03-29 11:07:58 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2?
sbonazzo: exception?
nsednev: testing_plan_complete+
rule-engine: planning_ack?
sbonazzo: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86304 0 master MERGED ansible: Get only active network interfaces for setting ovirtmgmt bridge 2018-09-03 09:35:54 UTC
oVirt gerrit 87240 0 ovirt-hosted-engine-setup-2.2 MERGED ansible: Get only active network interfaces for setting ovirtmgmt bridge 2018-02-07 08:46:03 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.