nova_wait_for_compute_service can be run before nova_api is up on controllers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| tripleo |
High
|
Oliver Walsh |
Bug Description
Initially reported here:
https:/
Both nova_api & nova_wait_
If we have controllers & computes, we have no way to tell nova_wait_
We need to look if we can move nova_wait_
tags: | added: stein-backport-potential |
Oliver Walsh (owalsh) wrote : | #1 |
Oliver Walsh (owalsh) wrote : | #2 |
But would that still race? Isn't paunch just launching the docker/podman command and returning immediately? So at the end of step 4 we can't assume nova_api is running - podman/docker could still be pulling the image.
Changed in tripleo: | |
assignee: | nobody → Oliver Walsh (owalsh) |
Fix proposed to branch: master
Review: https:/
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 8a87cbcc349feb9
Author: Oliver Walsh <email address hidden>
Date: Mon Sep 9 15:48:23 2019 +0100
Ensure nova-api is running before starting nova-compute containers
If nova-api is delayed starting then the nova_wait_
can timeout. A deployment using a slow/busy remote container repository is
particularly susceptible to this issue. To resolve this nova_compute and
nova_
has been added to step_4 to ensure nova_api is active before proceeding.
Change-Id: I6fcbc5cb5d4f3c
Closes-bug: #1842948
Changed in tripleo: | |
status: | In Progress → Fix Released |
Fix proposed to branch: stable/stein
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 11.3.0 | #6 |
This issue was fixed in the openstack/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit d80d948fe706420
Author: Martin Schuppert <email address hidden>
Date: Mon Oct 14 14:43:29 2019 +0200
Fix placement_
This fix the indent and volumes of the placement_
and the corresponding placement_
config of the extracted placement service.
It also
* changes to set placement:
instead of placement:
deprecated and not supported by placement:
* sets placement:
Related-Bug: 1842948
Change-Id: Ic24cf646efdd70
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-heat-templates (stable/train) | #8 |
Related fix proposed to branch: stable/train
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 20b485fe8e58110
Author: Oliver Walsh <email address hidden>
Date: Mon Sep 9 15:48:23 2019 +0100
Ensure nova-api is running before starting nova-compute containers
If nova-api is delayed starting then the nova_wait_
can timeout. A deployment using a slow/busy remote container repository is
particularly susceptible to this issue. To resolve this nova_compute and
nova_
has been added to step_4 to ensure nova_api is active before proceeding.
Conflicts:
deploymen
deploymen
Note: Since this is not a direct cherry-pick due to the placement
extraction in train release, this backport also includes needed
changed from https:/
Change-Id: I6fcbc5cb5d4f3c
Closes-bug: #1842948
(cherry picked from commit 8a87cbcc349feb9
tags: | added: in-stable-stein |
> We need to look if we can move nova_wait_ for_compute_ service to the step 5.
IIRC it's there to ensure the nova_compute has initialised before the cell_v2 host discovery in step 5...
Maybe add a step 6 (just for docker, not puppet).