docker services running as detached need better failure checking
Bug #1695540 reported by
Tim Rozet
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
High
|
Unassigned |
Bug Description
When running an openstack service as detached, a configuration error will cause services to not start correctly. For example, neutron server with missing plugin config will result in neutron not starting correctly. In docker the service will be shown as constantly restarting. However, OOO will continue deployment and think the service deployment was successful. This results in a false positive that the deployment succeeded. We should add checks after issuing the docker run to detached services to ensure they are not stuck in restarting state.
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → pike-rc2 |
Changed in tripleo: | |
milestone: | pike-rc2 → queens-1 |
Changed in tripleo: | |
status: | In Progress → Triaged |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
There is related spec for health-checks https:/ /review. openstack. org/#/c/ 465633/