scenario001/2-multinode-oooq-container deployment fails and timesout, containers not deployed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
wes hayutin |
Bug Description
scenario001 and scenario002 have been running red for about 24 hours [1-2]. They have been timing out during the overcloud deployment so we never have collected all the logs from the deployment.
Slagle pointed out the issue may be found in
http://
and caused by:
https:/
Testing a revert here:
https:/
[1] http://
[2] http://
[2] http://
Changed in tripleo: | |
assignee: | nobody → wes hayutin (weshayutin) |
status: | Triaged → In Progress |
http:// logs.openstack. org/23/ 540323/ 3/check/ tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 2e8cc91/ logs.openstack. org/45/ 521545/ 19/check/ tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 77cdaea/ logs.openstack. org/19/ 537719/ 1/gate/ tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 18be002/ logs.openstack. org/85/ 540385/ 1/check/ tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ df4505c/ logs.openstack. org/23/ 540323/ 2/check/ tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 4fcc6f9/ logs.openstack. org/45/ 521545/ 19/check/ tripleo- ci-centos- 7-scenario002- multinode- oooq-container/ 18acd6c/ logs.openstack. org/19/ 537719/ 1/gate/ tripleo- ci-centos- 7-scenario002- multinode- oooq-container/ 92dbe8b/
http://
http://
http://
http://
http://
http://