Comparing vxlan_networking log in both kind of jobs, they don't appear to do the same
The one with vxlan_network ssh problem: http://logs.openstack.org/43/563843/3/gate/tripleo-ci-centos-7-undercloud-containers/462364e/logs/undercloud/home/zuul/vxlan_networking.sh.log.txt.gz
The one with vxlan_networking passing: http://logs.openstack.org/82/562282/8/gate/tripleo-ci-centos-7-containers- multinode/07ab872/logs/undercloud/home/zuul/vxlan_networking.sh.log.txt.gz
Also in the last one there is a Failed to get unit file state for neutron-openvswitch-agent.service: No such file or directory 2018-04-25 13:08:14 | + '[' '' = enabled ']' doesn't look good.
Comparing vxlan_networking log in both kind of jobs, they don't appear to do the same
The one with vxlan_network ssh problem: logs.openstack. org/43/ 563843/ 3/gate/ tripleo- ci-centos- 7-undercloud- containers/ 462364e/ logs/undercloud /home/zuul/ vxlan_networkin g.sh.log. txt.gz
http://
The one with vxlan_networking passing: logs.openstack. org/82/ 562282/ 8/gate/ tripleo- ci-centos- 7-containers- 07ab872/ logs/undercloud /home/zuul/ vxlan_networkin g.sh.log. txt.gz
http://
multinode/
Also in the last one there is a openvswitch- agent.service: No such file or directory
Failed to get unit file state for neutron-
2018-04-25 13:08:14 | + '[' '' = enabled ']' doesn't look good.