Bug 1497916 - Host deploy failed - Failed to execute Ansible host-deploy role - TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt]
Summary: Host deploy failed - Failed to execute Ansible host-deploy role - TASK [ovirt...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Host-Deploy
Version: 4.2.0
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Dominik Holler
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-03 06:32 UTC by Michael Burman
Modified: 2017-12-20 11:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-12-20 11:34:28 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)
logs (254.37 KB, application/x-gzip)
2017-10-03 06:32 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82487 0 'None' MERGED core: Use IP address instead of network during install 2020-09-14 12:54:47 UTC

Description Michael Burman 2017-10-03 06:32:01 UTC
Created attachment 1333498 [details]
logs

Description of problem:
Host deploy failed - Failed to execute Ansible host-deploy role - TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt]

Add host failing on latest master because of failure to execute Ansible host-deploy role

[DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 
'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions.
 This feature will be removed in a future release. Deprecation warnings can be 
disabled by setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: include is kept for backwards compatibility but usage is
 discouraged. The module documentation details page may explain more about this
 rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-host-deploy-facts : Fetch info about VDSM] *************************
ok: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-host-deploy-facts : Set facts] *************************************
ok: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-provider-ovn-driver : Install ovirt-provider-ovn-driver] ***********
ok: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-provider-ovn-driver : Ensure ovn-controller is started] ************
changed: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-provider-ovn-driver : Ensure Open vSwitch is started] **************
changed: [orchid-vds2.qa.lab.tlv.redhat.com]

TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt] *********************
fatal: [orchid-vds2.qa.lab.tlv.redhat.com]: FAILED! => {"changed": true, "cmd": ["vdsm-tool", "ovn-config", "10.35.161.233", "ovirtmgmt"], "delta": "0:00:00.969424", "end": "2017-10-03 09:11:42.165043", "failed": true, "msg": "non-zero return code", "rc": 1, "start": "2017-10-03 09:11:41.195619", "stderr": "Traceback (most recent call last):\n  File \"/usr/bin/vdsm-tool\", line 219, in main\n    return tool_command[cmd][\"command\"](*args)\n  File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 58, in ovn_config\n    ip_address = get_ip_addr(get_network(network_caps(), net_name))\n  File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 79, in get_network\n    raise NetworkNotFoundError(net_name)\nNetworkNotFoundError: ovirtmgmt", "stderr_lines": ["Traceback (most recent call last):", "  File \"/usr/bin/vdsm-tool\", line 219, in main", "    return tool_command[cmd][\"command\"](*args)", "  File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 58, in ovn_config", "    ip_address = get_ip_addr(get_network(network_caps(), net_name))", "  File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 79, in get_network", "    raise NetworkNotFoundError(net_name)", "NetworkNotFoundError: ovirtmgmt"], "stdout": "", "stdout_lines": []}

PLAY RECAP *********************************************************************
orchid-vds2.qa.lab.tlv.redhat.com : ok=6    changed=2    unreachable=0    failed=1 


Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171002190603.git3015ada.el7.centos

How reproducible:
100% Seems to be on latest master

Steps to Reproduce:
1. Try to add new host to latest master


Actual results:
Install failed

Expected results:
Should work

Additional info:

Comment 1 Michael Burman 2017-10-03 06:33:26 UTC
Try to re-install and get - Error while executing action: 

orchid-vds2.qa.lab.tlv.redhat.com:
Cannot edit Host. The provider type should be 'OpenStack Networking'.

2017-10-03 09:32:12,461+03 WARN  [org.ovirt.engine.core.bll.hostdeploy.InstallVdsCommand] (default task-7) [dac756ff-04a7-434c-8a05-7c0387b9e54c] Validation of action 'InstallVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__HOST,ACTION_TYPE_FAILED_PROVIDER_TYPE_MISMATCH


Dan, is it our new regression?

Comment 2 Germano Veit Michel 2017-10-03 06:49:59 UTC
Also hit the same. Doing Setup Host Networks on the failed install host, assigning the ovirtmgmt network clicking OK seems to do the trick.

Comment 3 Dan Kenigsberg 2017-10-03 06:56:36 UTC
Yes, and I believe Dominik is working to fix it.

Comment 4 Dominik Holler 2017-10-03 08:30:08 UTC
Only clusters existing during engine-setup, e.g. cluster 'Default', are affected.
As a temporary solution a new cluster, e.g. a recreated 'Default', will work.

Comment 5 Mor 2017-10-30 09:34:45 UTC
Verified on:
4.2.0-0.0.master.20171027213842.gitded437c.el7.centos

Comment 6 Sandro Bonazzola 2017-12-20 11:34:28 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, 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.