Back to bug 1327603

Who When What Removed Added
John Prause 2016-04-15 13:11:53 UTC Depends On 1325167
Chris Pelland 2016-05-03 14:15:20 UTC Target Release 5.5.4 5.5.5
Dave Johnson 2016-05-18 18:00:39 UTC QA Contact dajohnso kzvyahin
Kyrylo Zvyagintsev 2016-05-25 15:14:49 UTC Whiteboard vm:retirement
Lucy Fu 2016-06-15 14:05:05 UTC Status ASSIGNED POST
CC lufu
John Prause 2016-06-15 14:19:58 UTC Status POST MODIFIED
errata-xmlrpc 2016-06-29 14:40:33 UTC Status MODIFIED ON_QA
Kyrylo Zvyagintsev 2016-07-07 11:51:31 UTC Status ON_QA VERIFIED
John Prause 2016-07-13 18:53:32 UTC Fixed In Version 5.5.5.0
Marianne Feifer 2016-07-19 19:43:47 UTC CC mfeifer
Doc Text Cause: Retired instances may be left in suspended state on Openstack server.

Consequence: Retired instance can be resume from provider

Fix: Add built in policy for event vm_resume.The build in policy will keep the retired instance remained in powered off state if it is powered on from the Openstack server.

Result:
Suyog Sainkar 2016-07-25 06:15:30 UTC CC ssainkar
Doc Text Cause: Retired instances may be left in suspended state on Openstack server.

Consequence: Retired instance can be resume from provider

Fix: Add built in policy for event vm_resume.The build in policy will keep the retired instance remained in powered off state if it is powered on from the Openstack server.

Result:
In the previous version of CloudForms, retired instances may be left in suspended state on OpenStack server. As a result, the retired instance could be resumed back to active state from the provider side (OpenStack) and this state was not refreshed back in CloudForms.
This update adds built in policy for event vm_resume. This policy will keep the retired instance in powered off state, even if it is powered on from the OpenStack server.
errata-xmlrpc 2016-07-26 14:44:18 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-07-26 15:32:21 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-07-26 11:32:21 UTC

Back to bug 1327603