Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1425206 - Retirement of a Vm or Instance should not delete it from the database
Retirement of a Vm or Instance should not delete it from the database
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.7.0
Unspecified Unspecified
high Severity high
: GA
: 5.8.0
Assigned To: William Fitzgerald
Mike Shriver
retirement
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-20 15:23 EST by Tina Fitzgerald
Modified: 2017-05-31 10:35 EDT (History)
5 users (show)

See Also:
Fixed In Version: 5.8.0.7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-05-31 10:35:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1367 normal SHIPPED_LIVE Moderate: CFME 5.8.0 security, bug, and enhancement update 2017-05-31 14:16:03 EDT

  None (edit)
Description Tina Fitzgerald 2017-02-20 15:23:12 EST
Description of problem: 

Retirement of a Vm or Instance should not delete it from the database.  Retirement should remove the Vm or Instance from the provider but the Vm or Instance should still be in the database.

Original Ticket
https://bugzilla.redhat.com/show_bug.cgi?id=1331567
Comment 2 Tina Fitzgerald 2017-04-03 10:06:59 EDT
This issue has been resolved:
https://github.com/ManageIQ/manageiq-content/pull/55
Comment 3 Mike Shriver 2017-05-18 08:49:08 EDT
Tested against CFME 5.8.0.14 with rhevm and ec2 providers.

Instances/VMs retired through the CFME UI are not deleted from the VMDB, and their records are maintained.

This allows administrators to un-retire resources when available, and to maintain accurate C&U/chargeback metrics.
Comment 5 errata-xmlrpc 2017-05-31 10:35:36 EDT
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/RHSA-2017:1367

Note You need to log in before you can comment on or make changes to this bug.