| 2017-04-03 09:42:13 |
Lucian Petrut |
description |
In some cases, during failovers, the instances are stopped before being moved. Nova gets the according power state change event and if the instance has not been moved/started already, it will mark it as stopped. When the instance finally starts, Nova treats it as an unexpected state change and power it back off. |
In some cases, during failovers, the instances are stopped before being moved. Nova gets the according power state change event and if the instance has not been moved/started already, it will mark it as stopped.
When the instance finally starts, Nova treats it as an unexpected state change and power it back off. |
|
| 2018-11-01 08:34:51 |
Lucian Petrut |
description |
In some cases, during failovers, the instances are stopped before being moved. Nova gets the according power state change event and if the instance has not been moved/started already, it will mark it as stopped.
When the instance finally starts, Nova treats it as an unexpected state change and power it back off. |
In some cases, during failovers, the instances are stopped before being moved. Nova gets the according power state change event and if the instance has not been moved/started already, it will mark it as stopped.
When the instance finally starts, Nova treats it as an unexpected state change and power it back off.
The current workaround is to avoid instance lifecycle events handling. |
|
