Back to bug 1303096

Who When What Removed Added
John Prause 2016-01-29 14:33:16 UTC Keywords ZStream
Status NEW ON_DEV
Target Release 5.6.0 5.5.3
Assignee gmccullo tfitzger
Tina Fitzgerald 2016-02-29 18:15:47 UTC Status ON_DEV POST
John Prause 2016-02-29 21:00:44 UTC Status POST MODIFIED
Marianne Feifer 2016-03-02 20:49:39 UTC CC mfeifer
Doc Text Cause: If this retirement state machine is executed from a "UI" zone that does not have automate enabled the request is queued for the wrong zone.

Consequence: Retiring a service is not executed in the zone that the vm's ems belongs to.

Fix: Clear zone if automate role not enabled.

Result: Retirement executed in the correct zone.
errata-xmlrpc 2016-03-22 10:58:11 UTC Status MODIFIED ON_QA
John Prause 2016-03-22 12:31:50 UTC Fixed In Version 5.5.3.2
Dayle Parker 2016-03-23 03:41:58 UTC Doc Text Cause: If this retirement state machine is executed from a "UI" zone that does not have automate enabled the request is queued for the wrong zone.

Consequence: Retiring a service is not executed in the zone that the vm's ems belongs to.

Fix: Clear zone if automate role not enabled.

Result: Retirement executed in the correct zone.
Previously, when service retirement was executed in the CloudForms Management Engine Appliance from a zone without the automate role enabled, the request was queued in the wrong zone. This prevented the virtual machine and service from being retired. Now, when retiring a service, the zone parameter is cleared if the automate role is not enabled, and retirement executes in the correct zone regardless of automate configuration.
Dayle Parker 2016-03-24 01:18:54 UTC Doc Text Previously, when service retirement was executed in the CloudForms Management Engine Appliance from a zone without the automate role enabled, the request was queued in the wrong zone. This prevented the virtual machine and service from being retired. Now, when retiring a service, the zone parameter is cleared if the automate role is not enabled, and retirement executes in the correct zone regardless of automate configuration. Previously, when service retirement was executed in the CloudForms Management Engine Appliance from a zone without the Automate role enabled, the request was queued in the wrong zone. This prevented the virtual machine and service from being retired. Now, when retiring a service, the zone parameter is cleared if the Automate role is not enabled, and retirement executes in the correct zone regardless of Automate configuration.
dajohnso 2016-03-24 21:12:55 UTC QA Contact dajohnso anewman
Alex Newman 2016-04-05 14:15:36 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-04-13 03:47:03 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-13 18:42:24 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-13 14:42:24 UTC

Back to bug 1303096