UPDATE_REPLACE deletes things before it creates the replacement
Bug #1176142 reported by
Clint Byrum
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Fix Released
|
High
|
Zane Bitter | ||
Bug Description
If I change the flavor (instance type) of my server in an update to my stack, I expect it to be replaced. However, I expect that it will be replaced by:
* create new server
* update dependent resources
* delete old server
However, Heat currently does it the other way
* delete old server
* create new server
* update continues (thus updating dependent resources)
This is quite broken, as if a memcache server is deleted and then re-created any dependent resources will be *down* until that new memcache server reaches the 'active' state (and maybe longer if waitconditions are involved)
| description: | updated |
Revision history for this message
| Steven Hardy (shardy) wrote | #1 |
| Changed in heat: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Steven Hardy (shardy) wrote | #2 |
| Changed in heat: | |
| assignee: | nobody → Zane Bitter (zaneb) |
| Changed in heat: | |
| milestone: | none → havana-2 |
| Changed in heat: | |
| status: | Confirmed → In Progress |
| Changed in heat: | |
| milestone: | havana-2 → havana-3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to heat (master) | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (master) | #4 |
| Changed in heat: | |
| status: | In Progress → Fix Committed |
| Changed in heat: | |
| status: | Fix Committed → Fix Released |
| Changed in heat: | |
| milestone: | havana-3 → 2013.2 |
To post a comment you must log in.
Yeah, I can confirm this - I wrote the initial UpdateStack code, and I did it this way as it was the simplest way to get things working, agree we should take another look at this and improve it.