There seems to be a bug with tumbleweed and openvswitch.
The integration job fails with [1]
2018-03-27 08:12:44.524005 | TASK [multi-node-bridge : Ensure openvswitch is started]
2018-03-27 08:12:45.546845 | secondary | ERROR: Unable to start service openvswitch: A dependency job for openvswitch.service failed. See 'journalctl -xe' for details.
2018-03-27 08:12:45.586488 | primary | ERROR: Unable to start service openvswitch: A dependency job for openvswitch.service failed. See 'journalctl -xe' for details.
If you install openvswitch on a suse host, it fails to start. The
journal contains
ovsdb-server[29316]: ovs|00002|daemon_unix|EMER|/var/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied)
ovs-ctl[29267]: ovsdb-server: /var/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied)
ovs-ctl[29267]: Starting ovsdb-server ... failed!
systemd[1]: ovsdb-server.service: Control process exited, code=exited status=1
systemd[1]: ovsdb-server.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Open vSwitch Database Unit.
This appears to be the same problem as [2] which boils down to a
systemd/openvswitch incompatability. Pending reporting and fixing
this upstream, make the test non-voting.
[1] http://logs.openstack.org/76/556776/1/check/openstack-infra-multinode-integration-opensuse-tumbleweed/393fa10/job-output.txt.gz#_2018-03-27_08_12_44_524005
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1508495
Change-Id: I6ce5b14713a341c6c90ac860f6f843cf3d014abc
7387784bc6