Back to bug 1298986
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Taras Lehinevych | 2016-01-15 15:55:04 UTC | CC | tlehinev | |
| Severity | unspecified | high | ||
| Greg Blomquist | 2016-01-21 15:14:27 UTC | Priority | unspecified | high |
| Status | NEW | ASSIGNED | ||
| Assignee | gblomqui | lsmola | ||
| Taras Lehinevych | 2016-01-22 12:02:01 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | NOTABUG | ||
| Last Closed | 2016-01-22 07:02:01 UTC | |||
| Shikha | 2016-02-10 06:21:51 UTC | CC | snansi | |
| Doc Text | In the current version of CloudForms Management Engine, it is not usually possible to run a virtual machine after it has been retired. But, the OpenStack provider still allows a retired virtual machine to be powered on from the OpenStack console. This will result in CloudForms Management Engine reporting the virtual machine to be powered on while retired. In this case, retiring the virtual machine has to be enforced by the CloudForms Management Engine administrator. For example: - Change the State Machine workflow and define the end state of the retired virtual machine to be deleted or removed from provider inventory instead of being stopped or suspended. - Write a Control Policy that watches the provider for virtual machine Start Events and shut down the virtual machine if it has been retired. |
|||
| John Skeoch | 2016-08-03 01:33:42 UTC | CC | dajohnso |
Back to bug 1298986