Bug 1346962 - Only delete cloudforms provisioned vm's when retiring
Summary: Only delete cloudforms provisioned vm's when retiring
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Tina Fitzgerald
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-15 17:55 UTC by John Hardy
Modified: 2018-04-10 15:44 UTC (History)
10 users (show)

Fixed In Version: 5.6.0.12
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 16:07:34 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description John Hardy 2016-06-15 17:55:46 UTC 
Change/revert automate to cover the following 

By DEFAULT, CF will delete machines/instances that CF provisioned when retirement is executed. CF will NOT delete machines it had not provisioned.
Comment 2 Greg McCullough 2016-06-15 18:16:23 UTC 
This logic was introduced in PR https://github.com/ManageIQ/manageiq/pull/6290 based on work in Bug 1300559.

We will revert the logic as per PM.
Comment 3 Greg McCullough 2016-06-15 19:32:24 UTC 
Change made in PR https://github.com/ManageIQ/manageiq/pull/9233
Comment 4 Oleg Barenboim 2016-06-16 16:50:40 UTC 
PR merged and backported to Darga
Comment 7 errata-xmlrpc 2016-06-29 16:07:34 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348
Note You need to log in before you can comment on or make changes to this bug.