CI timing out with no logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Gregory Haynes |
Bug Description
I've been seeing a lot of CI jobs timing out with no logs to help debug the problem. Opening this bug to have a place to track those issues (there are multiple similar but different symptoms).
One example:
2014-12-19 17:58:43.187 | Waiting for the overcloud stack to be ready
2014-12-19 17:58:43.187 | + wait_for_
2014-12-19 19:50:02.083 | 2014-12-19 19:50:02,060 - testenv-client - ERROR - The command hasn't completed but the testenv worker has released the environment. Killing all processes.
2014-12-19 19:50:02.129 | /opt/stack/
2014-12-19 19:50:02.138 | ERROR: the main setup script run by this job failed - exit code: 137
2014-12-19 19:50:02.139 | please look at the relevant log files to determine the root cause
And no seed_logs collected to determine why the deployment didn't complete in a reasonable time: http://
Changed in tripleo: | |
assignee: | nobody → Gregory Haynes (greghaynes) |
status: | Triaged → In Progress |
Changed in tripleo: | |
importance: | Medium → High |
It does not seem to be related to the distro, I got it with the precise job check-tripleo- ironic- overcloud- precise- nonha