CI failing in <10s with "traceroute: not found"

Bug #1564578 reported by John Trowbridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

The fix for the other critical CI failure[1] is failing very quickly in a way that I am not even sure is tripleo related.

It seems like the root cause is the traceroute command not being found[2], but I am not even sure what is running that /tmp/hudson*.sh script.

Raising this as a critical alert bug since all CI is failing this way.

[1] https://review.openstack.org/#/c/300142
[2] http://logs.openstack.org/42/300142/1/check-tripleo/gate-tripleo-ci-f22-nonha/bf67b1d/console.html#_2016-03-31_19_00_28_758

Tags: alert
Revision history for this message
Ben Nemec (bnemec) wrote :

Infra has resolved the problem causing this.

Changed in tripleo:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.