Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1331567 - 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.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.6.0
Assigned To: William Fitzgerald
Kyrylo Zvyagintsev
vm:retirement
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-28 16:21 EDT by William Fitzgerald
Modified: 2016-06-29 11:56 EDT (History)
5 users (show)

See Also:
Fixed In Version: 5.6.0.6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-29 11:56:06 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 RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description William Fitzgerald 2016-04-28 16:21:52 EDT
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.


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Navigate to /Infrastructure/Virtual Machines/
2. Select a Vm
3. Click on 'Lifecycle' button and select 'Retire selected items'


Actual results:
If retirement is successful, you will no longer be able to view the Vm/Instance


Expected results:
If retirement is successful, you will still be able to view the Vm/Instance.




Additional info:
Comment 3 CFME Bot 2016-05-04 12:06:01 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/c9fcd6a45c8837e154dcd60b222ea2041d0e6878

commit c9fcd6a45c8837e154dcd60b222ea2041d0e6878
Author:     william fitzgerald <wfitzger@redhat.com>
AuthorDate: Wed Apr 27 16:36:45 2016 -0400
Commit:     william fitzgerald <wfitzger@redhat.com>
CommitDate: Fri Apr 29 10:01:37 2016 -0400

    Change retirement default behavior NOT to delete from vmdb.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1331567

 .../Cloud/VM/Retirement/StateMachines/VMRetirement.class/__class__.yaml | 2 +-
 .../Cloud/VM/Retirement/StateMachines/VMRetirement.class/default.yaml   | 2 +-
 .../VM/Retirement/StateMachines/VMRetirement.class/__class__.yaml       | 2 +-
 .../VM/Retirement/StateMachines/VMRetirement.class/default.yaml         | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
Comment 7 errata-xmlrpc 2016-06-29 11:56:06 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/RHBA-2016:1348

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