Bug 1692941 - Retiring an embedded Ansible service always retires the service resources
Summary: Retiring an embedded Ansible service always retires the service resources
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.11.0
Assignee: drew uhlmann
QA Contact: Satyajit Bulage
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1677548
Blocks: 1695627
TreeView+ depends on / blocked
 
Reported: 2019-03-26 17:28 UTC by Peter McGowan
Modified: 2019-12-13 14:57 UTC (History)
6 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1695627 (view as bug list)
Environment:
Last Closed: 2019-12-13 14:57:17 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter McGowan 2019-03-26 17:28:17 UTC
Description of problem:
Retiring an embedded Ansible service always retires the service resources, even if the service definition has "Remove Resources" set to "no"

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

How reproducible:
Every time

Steps to Reproduce:
1. Create an embedded Ansible service that either creates a VM, or subsequently assign a VM to the service. In the service retirement definition ensure "Remove Resources" is set to "no"
2. Provision the service, and ensure that the resulting service in "My Services" has a VM associated with it.
3. Retire the service

Actual results:
The VM is also retired

Expected results:
The VM should not be retired

Additional info:
The Retire_Advanced_Resource_None state machine is confirmed as running, which should not retire the service resources

Comment 3 drew uhlmann 2019-04-01 17:16:14 UTC
https://github.com/ManageIQ/manageiq/pull/18609

Comment 5 Satyajit Bulage 2019-08-25 16:43:15 UTC
After setting Retirement option to "No", Retire service is not retiring resource attached to it.

Verified Version: 5.11.0.21.20190821214526_b0060d0


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