Bug 1331567

Summary:	Retirement of a Vm or Instance should not delete it from the database
Product:	Red Hat CloudForms Management Engine	Reporter:	William Fitzgerald <wfitzger>
Component:	Automate	Assignee:	William Fitzgerald <wfitzger>
Status:	CLOSED ERRATA	QA Contact:	Kyrylo Zvyagintsev <kzvyahin>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.6.0	CC:	jhardy, mkanoor, obarenbo, simaishi, tfitzger
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	vm:retirement
Fixed In Version:	5.6.0.6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-29 15:56:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description William Fitzgerald 2016-04-28 20:21:52 UTC

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 2 CFME Bot 2016-04-29 14:55:46 UTC

https://github.com/ManageIQ/manageiq/pull/8302

Comment 3 CFME Bot 2016-05-04 16:06:01 UTC

New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/c9fcd6a45c8837e154dcd60b222ea2041d0e6878

commit c9fcd6a45c8837e154dcd60b222ea2041d0e6878
Author:     william fitzgerald <wfitzger>
AuthorDate: Wed Apr 27 16:36:45 2016 -0400
Commit:     william fitzgerald <wfitzger>
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 4 CFME Bot 2016-05-17 17:22:20 UTC

https://github.com/ManageIQ/manageiq/pull/8473

Comment 7 errata-xmlrpc 2016-06-29 15:56:06 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