Bug 1565418

Summary: Service retirement does not properly handle retiring orchestration stacks
Product: Red Hat CloudForms Management Engine Reporter: Jeff Warnica <jwarnica>
Component: AutomateAssignee: Tina Fitzgerald <tfitzger>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, jwarnica, mkanoor, obarenbo, tfitzger
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-18 14:32:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Warnica 2018-04-10 01:27:24 UTC
Description of problem:

Attempting to smoke test an AWS CloudFormations stack lifeclye, noticed that the service retirement does not work. This is provider independent and would also fail for other orchestration templates / stacks / service catalog combinations.


How reproducible:
always

Steps to Reproduce:
1. Deploy a new Orchestration template
2. Generate a Dialog. Wire up to a new service catalog item
3. Order SC item
4. Retire SC item

Actual results:
Attached stack does not retire and remains

Expected results:
Attached stack does retire

Additional info:

Proposed fix:

/ Service / Retirement / StateMachines / Methods / retire_service

+$evm.root["service"].orchestration_stack.retire_now

(possibly with nil check)

Comment 2 Tina Fitzgerald 2018-05-25 13:51:53 UTC
Hi Jeff,

Could you supply more details, and logs, or preferably a reproducer environment?

Thanks,
Tina

Comment 3 Tina Fitzgerald 2018-06-18 16:03:06 UTC
Hi Jeff,

Per comment 2, could you supply more detail?

Thanks,
Tina

Comment 4 Jeff Warnica 2018-06-18 16:12:41 UTC
There is no special environment needed.

Per my steps, create dialog and catalog item, provision a stack, and attempt to retire the stack. It won't be removed.

Comment 5 Tina Fitzgerald 2018-06-18 16:20:42 UTC
Hi Jeff,

In what version of 5.9 did you encounter this issue?

Thanks,
Tina

Comment 6 Jeff Warnica 2018-06-18 16:30:16 UTC
I believe I found it on an appliance which is now at 5.9.2, but well could have been before that upgrade happened.

Comment 7 Tina Fitzgerald 2018-07-18 14:32:58 UTC

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