Undercloud deploy is not idempotent
Bug #1686716 reported by
Bogdan Dobrelya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Description:
For undercloud deploy the stack is newly created every time, nothing is persisted: that is expected and not a bug.
Although, it seemingly always restarts the containers, even when the images and its configs are the same. And it does so via 'docker rm' and 'docker run'.
Expected:
* secrets/passwords should not be changing each time (shardy has a WIP patch for that in https:/
* containers should be restarted only if images or configs have been updated
| Changed in tripleo: | |
| milestone: | none → pike-2 |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: containers idempotency |
Revision history for this message
| Dan Prince (dan-prince) wrote | #1 |
| tags: | removed: idempotency |
| summary: |
- Undercloud deploy is not idempotent and takes a hard way to re-apply + Undercloud deploy is not idempotent |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in tripleo: | |
| milestone: | queens-1 → queens-2 |
| Changed in tripleo: | |
| milestone: | queens-2 → queens-3 |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #3 |
| Changed in tripleo: | |
| status: | Triaged → Fix Committed |
| Changed in tripleo: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The new t-h-t was specifically designed not to reused an existing stack. Aside from the password and containers issues you mentioned above please do note that currently the heat stack was actually designed to be ephemeral in this regard.