Bug 1720338 - Cannot retire service which has a VM that has been retired first
Summary: Cannot retire service which has a VM that has been retired first
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.10.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.11.0
Assignee: drew uhlmann
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1728889
TreeView+ depends on / blocked
 
Reported: 2019-06-13 17:57 UTC by Tuan
Modified: 2019-12-13 15:01 UTC (History)
8 users (show)

Fixed In Version: 5.11.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1728889 (view as bug list)
Environment:
Last Closed: 2019-12-13 15:01:30 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 drew uhlmann 2019-06-14 12:15:22 UTC 
Could the customer please run a regular service retirement (with a VM) out of the box **without retiring the underlying VMs first** as a sanity check please and report back the outcome of that?
Comment 4 Tina Fitzgerald 2019-06-18 19:45:02 UTC 
Hi Tuan, 

As we discovered in our debugging session this afternoon, there is an issue in Service retirement where a retired Service VM will cause the service retirement to fail.

We create a retirement task for every service service_resource that is "retireable". The retireable check needs to be modified to include a check for retired.

Thanks for your work on this issue. We'll let you know once we have a fix.

Thanks,
Tina
Comment 5 drew uhlmann 2019-06-19 18:41:52 UTC 
https://github.com/ManageIQ/manageiq/pull/18895
Comment 8 juwatts 2019-07-02 19:54:16 UTC 
Verified in 5.11.0.11.20190625161125_392c61e

Verification Steps:
1) Create a dialogue, catalog, and new catalog item to provision a VM
2) Order a service to provision a new VM 
3) Retired the VM
4) Retired the Service

VM and Service both retired successfully. 

No ERRORs observed in the evm.log
Note You need to log in before you can comment on or make changes to this bug.