Bug 1309825 - un-retiring a VM does not unset the retirement_state field in vmdb
Summary: un-retiring a VM does not unset the retirement_state field in vmdb
Keywords:
Status: CLOSED DUPLICATE of bug 1297351
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.5.3
Assignee: Tina Fitzgerald
QA Contact: Dave Johnson
URL:
Whiteboard: vm:retirement:rest
Depends On: 1297351 1306830
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-18 18:53 UTC by John Prause
Modified: 2019-10-10 11:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1306830
Environment:
Last Closed: 2016-03-09 20:36:36 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 Tina Fitzgerald 2016-02-29 17:51:10 UTC 
Hi Colin,

Can you validate the information provided in "Additional comment from Tina Fitzgerald on 2016-02-17 14:58:46" resolves the customer reported issue in your environment?

The fixes made by Madhu are not intended to resolve this issue.

Let me know if you have any questions.

Thanks,
Tina
Comment 5 Colin Arnott 2016-03-08 16:19:37 UTC 
This bug contains current discussion: https://bugzilla.redhat.com/show_bug.cgi?id=1306830T
Comment 6 Tina Fitzgerald 2016-03-09 20:36:10 UTC 
This issue has been resolved by fixes contained in these tickets:

https://bugzilla.redhat.com/show_bug.cgi?id=1297351
https://bugzilla.redhat.com/show_bug.cgi?id=1299069

The default retirement state machine is designed to remove the VM from the provider and the VMDB. In that case, there would be no VM to unretire.
Comment 7 Tina Fitzgerald 2016-03-09 20:36:36 UTC 

*** This bug has been marked as a duplicate of bug 1297351 ***
Note You need to log in before you can comment on or make changes to this bug.