rollback may replace instances, but sometimes it's not needed.
Bug #1439722 reported by
Ethan Lynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Ethan Lynn |
Bug Description
1. Create a server with flavor_larger
2. update this server to flavor_smaller
3. update will fail and start to rollback
4. After rollback complete, instance will be recreated.
If resize a instance with flavor smaller, nova will through an error and refuse to resize this instance, so the instance is still in status active, and nothing changed.
But heat catch that error and start to rollback, during rollback ,instance will be replace by a new one. But actually it's no need to create a new instance and kill the old one, just reverse the template is ok.
Changed in heat: | |
assignee: | nobody → Ethan Lynn (ethanlynn) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: fixed-by-convergence |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
I think this bug may wait for convergence ready and then try to fix it.