Upscaling container env fails due to missing volume when updating config
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
I tried to upscale a container environment using current tripleo-
This is what I did:
$ openstack overcloud deploy --templates tripleo-
-> run successfully
$ openstack overcloud deploy --templates tripleo-
-> Failed.
It looks like the reason is that the Swift proxy server is being restarted during the config update (of a non-Swift service?), but the Swift volume is not mounted and therefore rings are missing.
| Christian Schwede (cschwede) wrote | #1 |
| Christian Schwede (cschwede) wrote | #2 |
| summary: |
- Upscaling container env fails and restarts services outside containers + Upscaling container env fails due to missing volume when updating config |
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → pike-3 |
| tags: | added: containers |
| 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: | |
| 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 |
| Emilien Macchi (emilienm) wrote Cleanup EOL bug report | #3 |
| Changed in tripleo: | |
| importance: | High → Undecided |
| status: | Triaged → Expired |
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE