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.
This issue has been resolved:
Tested against CFME 220.127.116.11 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.
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.