Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1776302

Summary: 'A Network interface is required' error while hosted-engine deploy
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Polina <pagranat>
Component: NetworkAssignee: Asaf Rachmani <arachman>
Status: CLOSED NOTABUG QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.3.12CC: arachman, bugs, rbarry
Target Milestone: ---Flags: sbonazzo: planning_ack?
sbonazzo: devel_ack-
sbonazzo: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-18 09:06:48 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: 1795581    
Bug Blocks: 1459229    
Attachments:
Description Flags
ovirt-hosted-engine-setup none

Description Polina 2019-11-25 12:55:56 UTC 
Created attachment 1639471 [details]
ovirt-hosted-engine-setup

Description of problem:
hosted-engine deploy fails with RuntimeError: A Network interface is required

Version-Release number of selected component (if applicable):
rhvm-appliance-4.3-20191113.0.el7.x86_64
ovirt-hosted-engine-setup-2.3.12-1.el7ev.noarch
vdsm-4.30.38-1.el7ev.x86_64
baseurl=http://bob.eng.lab.tlv.redhat.com/builds/4.3/rhv-4.3.7-5/el$releasever 


How reproducible: 100%

Steps to Reproduce:
1. Create bond on host (host rhel 8.1)

[root@ocelot01 ~]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp23s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master my-bond state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
3: enp23s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master my-bond state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
11: my-bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
20: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:65:6a:75 brd ff:ff:ff:ff:ff:ff
21: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:65:6a:75 brd ff:ff:ff:ff:ff:ff

2. Run hosted-engine --deploy

Actual results:
Deployment fails:
2019-11-24 10:18:15,377+0200 DEBUG otopi.plugins.gr_he_common.network.bridge bridge._customization:149 {u'otopi_host_net': {u'changed': False, u'ansible_facts': {u'otopi_host_net': []}, u'_ansible_no_log': False}}
2019-11-24 10:18:15,377+0200 DEBUG otopi.context context._executeMethod:145 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py", line 159, in _customization
    raise RuntimeError(_('A Network interface is required'))
RuntimeError: A Network interface is required
2019-11-24 10:18:15,379+0200 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': A Network interface is required


Expected results:successful deployment

attached all the logs from ovirt-hosted-engine-setup/
The error is in ovirt-hosted-engine-setup-20191124101711-ng5psi.log

Additional info:
Comment 1 Sandro Bonazzola 2019-11-27 08:14:11 UTC 
11: my-bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff

root cause for this may be the name of the bond.
can you re-verify with bond0 instead of my-bond?
Comment 2 Polina 2019-11-28 13:00:55 UTC 
succeeded to deploy with bond0

ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp23s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
3: enp23s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:c8:a8:56 brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:c8:a8:56 brd ff:ff:ff:ff:ff:ff
7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:57:ae:82 brd ff:ff:ff:ff:ff:ff
Comment 3 Asaf Rachmani 2020-02-18 09:06:48 UTC 
Close it as NOTABUG as this is an oVirt restriction.