timeouts on wait_for nova list in tripleo-ci
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Derek Higgins |
Bug Description
Tripleo-ci seems to be having a lot of timeouts while waiting for the seed to initialize.
devdest_seed contains
wait_for 30 10 ping -c 1 192.0.2.1
<keystone initialization ....>
wait_for 30 10 nova list
The first wait_for is satisfied by configure.
So it looks like something between these two scripts has gotten slower or the keystone initialization has gotten faster
dib-run-parts Mon Feb 24 04:52:16 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:17 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:17 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:18 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:21 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:21 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:21 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:52:21 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:53:40 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:54:39 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:54:42 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:55:29 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:55:30 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:55:32 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:55:33 UTC 2014 Running /opt/stack/
dib-run-parts Mon Feb 24 04:58:24 UTC 2014 Running /opt/stack/
I compared how long it takes to run some of these scripts on the test env,
70-keystone (ci testenv 79s , locally 19s)
75-glance (ci testenv 59s , locally 16s)
80-nova-api (ci testenv 171s , locally 49s)
Do we just need to increase the timeout to allow for slower environments?