Bug 1662878 - HE deployment fails - Failed executing ansible-playbook in get_network_interfaces
Summary: HE deployment fails - Failed executing ansible-playbook in get_network_interf...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.3.0
: ---
Assignee: Ido Rosenzwig
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-02 09:57 UTC by Liran Rotenberg
Modified: 2019-10-22 08:13 UTC (History)
5 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.3.0
Clone Of:
Environment:
Last Closed: 2019-02-13 07:43:28 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3+
rule-engine: blocker+

Attachments (Terms of Use)
sosreport (9.76 MB, application/x-xz)
2019-01-02 09:57 UTC, Liran Rotenberg 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 96678 0 master MERGED Use ansible role's flag to collect network interfaces 2020-11-17 18:59:37 UTC

Description Liran Rotenberg 2019-01-02 09:57:56 UTC 
Created attachment 1517894 [details]
sosreport

Description of problem:
Deploying 4.3 HE fails.
2019-01-02 11:42:45,711+0200 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [oVirt.hosted-engine-setup : Validate selected bridge interface if management bridge does no
t exists]
2019-01-02 11:42:46,012+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 {u'msg': u'The selected network interface is not valid', u'changed': False, u'_ansible_no_log': F
alse}
2019-01-02 11:42:46,113+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"}
2019-01-02 11:42:46,213+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2
2019-01-02 11:42:46,214+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [localhost] : ok: 9 changed: 0 unreachable: 0 skipped: 14 failed: 1
2019-01-02 11:42:46,214+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:187 ansible-playbook stdout:
2019-01-02 11:42:46,214+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:189  to retry, use: --limit @/usr/share/ovirt-hosted-engine-setup/ansible/get_network_interfaces.retry

2019-01-02 11:42:46,214+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stderr:
2019-01-02 11:42:46,214+0200 DEBUG otopi.context context._executeMethod:143 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py", line 149, in _customization
    r = ah.run()
  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run
    raise RuntimeError(_('Failed executing ansible-playbook'))
RuntimeError: Failed executing ansible-playbook


Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.3.0-0.2.master.20181230140118.gitf06e728.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. On a fresh installed host, with 4.3 u/s repos run:
# hosted-engine --deploy


Actual results:
Deployment failed

Expected results:
Deployment succeed
Comment 1 Ido Rosenzwig 2019-01-02 10:54:24 UTC 
Which network interface did you chose ?
Are you sure the network interface you chose is present ?
Comment 2 Liran Rotenberg 2019-01-02 11:09:29 UTC 
(In reply to Ido Rosenzwig from comment #1)
> Which network interface did you chose ?
> Are you sure the network interface you chose is present ?

It didn't ask for any NIC. The only input requested is a pingable gateway IP address(which is OK for other deployments).
Comment 3 Ido Rosenzwig 2019-01-06 09:34:31 UTC 
Did you used an answerfile ? if so can you please attach it ?

Does your NIC configured as a bond or a bridge ?
Comment 4 Liran Rotenberg 2019-01-07 07:59:45 UTC 
As far as I remember, no answer file was in use.
The deploy command was without the --config-append.

About the NIC, I can't answer. I only know it was a fresh host after provision.
Comment 5 Red Hat Bugzilla Rules Engine 2019-01-09 09:04:13 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 6 Nikolai Sednev 2019-01-20 13:17:20 UTC 
ovirt-hosted-engine-setup-2.3.2-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.0-1.el7ev.noarch
rhvm-appliance-4.3-20190115.0.el7.x86_64

I successfully deployed HE over NFS using ethernet interface different than eth0.
Original error wasn't reproduced.
Moving to verified.
Comment 7 Greg Sheremeta 2019-02-12 18:57:52 UTC 
I'm now seeing this on master

ovirt-hosted-engine-setup-2.4.0-0.0.master.20190207093137.git480226b.el7.noarch
ovirt-hosted-engine-ha-2.4.0-0.0.master.20190207093429.20190207093423.git14e4066.el7.noarch
ovirt-engine-appliance-4.4-20190211.1.el7.x86_64

CentOS 7 1810 VM in virt-manager
Single interface, eth0 (the bare metal host is using a simple bridge on a 10g mellanox card)
yum update -y and rebooted
using cockpit to install self hosted engine.
It dies before getting to asking about storage

[ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Install oVirt Hosted Engine packages]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Install engine appliance]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Install ovirt-engine-appliance rpm]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Parse appliance configuration for path]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Parse appliance configuration for sha1sum]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Get OVA path]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Compute sha1sum]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Compare sha1sum]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : System configuration validations]
[ INFO ] TASK [ovirt.hosted_engine_setup : Detecting interface on existing management bridge]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Get all active network interfaces]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Filter bonds with bad naming]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Generate output list]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : debug]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"}


Same steps on the same bare metal host + updated CentOS 7 works fine with 4.3 release rpm.

Is it the same issue as above? Should I set back to ASSIGNED?
Comment 8 Sandro Bonazzola 2019-02-13 07:43:28 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 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.