Gate jobs are failing in different ways related to network issues
Bug #1766884 reported by
Gabriele Cerami
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Critical
|
Gabriele Cerami |
Bug Description
gate queue keeps resetting for problems not directly related to tripleo, that appear to be random but related with the network.
reset at 12 UTC caused by
queue is now going to reset with failures in various patches, on different job for a different reason than before,
Same error appeared in two different providers too
This is blocking also an important patch that is needed to fix promotion.
To post a comment you must log in.
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.