Bug 1720338

Summary: Cannot retire service which has a VM that has been retired first
Product: Red Hat CloudForms Management Engine Reporter: Tuan <tuado>
Component: ProvisioningAssignee: drew uhlmann <duhlmann>
Status: CLOSED CURRENTRELEASE QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.4CC: duhlmann, jhardy, juwatts, michael.moir, nansari, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1728889 (view as bug list) Environment:
Last Closed: 2019-12-13 15:01:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1728889    

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