Bug 1720244 - Retiring the multiple Services does not retire the VMs it associated
Summary: Retiring the multiple Services does not retire the VMs it associated
Keywords:
Status: CLOSED DUPLICATE of bug 1722194
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.10.6
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.10.7
Assignee: Tina Fitzgerald
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-13 13:31 UTC by Niyaz Akhtar Ansari
Modified: 2019-07-05 15:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-24 15:09:59 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
request page (129.99 KB, image/png)
2019-06-13 13:31 UTC, Niyaz Akhtar Ansari
no flags Details
evm and automation log (5.90 MB, application/x-tar)
2019-06-14 06:19 UTC, Niyaz Akhtar Ansari
no flags Details

Description Niyaz Akhtar Ansari 2019-06-13 13:31:39 UTC
Created attachment 1580297 [details]
request page

Description of problem:


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

How reproducible:
100%

Steps to Reproduce:
1.Provision the two service catalog items with vms
2.Go to my service-> select the both services 
3.Retire the services 

Actual results:
Services getting retired but it does not retire the VMs it associated.
It fails with error in request page.

Expected results:
VMs also should be retired 

Additional info:

Comment 2 Greg McCullough 2019-06-13 16:30:51 UTC
Please provide logs to support this case, thanks.

Comment 3 Niyaz Akhtar Ansari 2019-06-14 06:19:26 UTC
Created attachment 1580540 [details]
evm and automation log

Comment 4 Tina Fitzgerald 2019-06-24 15:09:59 UTC

*** This bug has been marked as a duplicate of bug 1722194 ***


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