On Sun, Oct 1, 2017 at 12:19 PM, Yedidyah Bar David <didi(a)redhat.com> wrote:
Hi all,
On Sun, Oct 1, 2017 at 10:15 AM, Code Review <gerrit(a)ovirt.org> wrote:
> Jenkins CI posted comments on this change.
>
> View Change
>
> Patch set 1:Continuous-Integration -1
>
> Build Failed
>
>
http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x8...
> : FAILURE
Above was triggered by [1].
It failed with [2]:
TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt] *********************
fatal: [lago-he-basic-suite-master-host1]: FAILED! => {"changed":
true, "cmd": ["vdsm-tool", "ovn-config",
"192.168.200.99",
"ovirtmgmt"], "delta": "0:00:00.623565", "end":
"2017-10-01
03:15:11.179717", "failed": true, "msg": "non-zero return
code", "rc":
1, "start": "2017-10-01 03:15:10.556152", "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": []}
Meaning, 'ovirtmgmt' is missing.
In host-deploy [3] of this host, I see that the engine asked
host-deploy to configure ovirtmgmt:
2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ### Customization phase, use
'install' to proceed
2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ### COMMAND>
2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND **%QHidden: FALSE
2017-10-01 03:14:36,037-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ***Q:STRING
CUSTOMIZATION_COMMAND
2017-10-01 03:14:36,037-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND **%QEnd:
CUSTOMIZATION_COMMAND
2017-10-01 03:14:36,038-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:RECEIVE env-query -k
HOSTED_ENGINE_CONFIG/bridge
2017-10-01 03:14:36,038-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND **%QStart:
HOSTED_ENGINE_CONFIG/bridge
2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ###
2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ### Please specify value for
'HOSTED_ENGINE_CONFIG/bridge':
2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ### Response is VALUE
HOSTED_ENGINE_CONFIG/bridge=type:value or ABORT
HOSTED_ENGINE_CONFIG/bridge
2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND ***Q:VALUE
HOSTED_ENGINE_CONFIG/bridge
2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND **%QEnd:
HOSTED_ENGINE_CONFIG/bridge
2017-10-01 03:14:36,040-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:RECEIVE VALUE
HOSTED_ENGINE_CONFIG/bridge=str:ovirtmgmt
2017-10-01 03:14:36,040-0400 DEBUG otopi.plugins.otopi.dialog.machine
dialog.__logString:204 DIALOG:SEND **%QStart:
CUSTOMIZATION_COMMAND
However, AFAIU this was deprecated quite a long time ago [4], and does
not appear in other runs, e.g. the latest succeeded run of the same
job [5][6]. Also, I can't see in engine log there [7] how ovirtmgmt
was created (if at all).
I now see a difference between them:
The successful one [7] passed to ansible:
--extra-vars=host_deploy_ovn_central=null
And the failed one [8] passed:
--extra-vars=host_deploy_ovn_central=192.168.200.99
So perhaps this was caused by a recent change related to OVN? Although
I looked at engine git log and can't find anything.
Many of project:ovirt-engine branch:master
topic:"ovirt-provider-ovn-driver deployment" have been merged have
been merged already (but kept check-patch very green). I hope Dominik
can read more into it.