Update timeout too long in CI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Looking through the logs on http://
Unfortunately, the job timeout means we get no logs for anything so it's going to be hard to debug this. It seems to be happening on a pretty regular basis right now though.
Logstash for general gate timeouts: http://
Changed in tripleo: | |
milestone: | none → pike-1 |
tags: | added: alert |
Changed in tripleo: | |
status: | Triaged → Fix Released |
tags: | removed: alert |
AFAICT the timeout is repected directly via heat:
(undercloud) [stack@undercloud ~]$ heat stack-create test -f hosts-config.yaml -e hosts_env.yaml -t 333
(undercloud) [stack@undercloud ~]$ heat stack-show test | grep timeout
WARNING (shell) "heat stack-show" is deprecated, please use "openstack stack show" instead
| timeout_mins | 333
And also via tripleoclient:
openstack overcloud deploy --templates --timeout 333
| timeout_mins | 333
Could this be an issue specific to CI, e.g we've messed up the deploy arguments?