If masakari recover "resized" instance that's state was "stopped" before resizing, it will be "active".
Bug #1690995 reported by
Rikimaru Honjo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
masakari |
Fix Released
|
High
|
Dinesh Bhor |
Bug Description
[Actual]
1. I called Stop API for an instance.
2. I called Resize API for an instance.
3. Host failure happened before resize confirming.
4. Masakari recovered the instance.
5. The instance's state gone to "active" after recovering.
[My Expectation]
I think that instance's state should be "stopped" after recovering if the state before resizing is "stopped".
[Remarks]
This report was split from https:/
description: | updated |
Changed in masakari: | |
assignee: | nobody → Dinesh Bhor (dinesh-bhor) |
Changed in masakari: | |
status: | New → In Progress |
Changed in masakari: | |
importance: | Undecided → High |
To post a comment you must log in.
IMO, we can detect the state before resizing by instance action list API.
Even if end-users shutoff in guest OS, that action history will be recorded.
But, we should discuss whether or not masakari should stop the active instance.