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)
Hi Jeff, Could you supply more details, and logs, or preferably a reproducer environment? Thanks, Tina
Hi Jeff, Per comment 2, could you supply more detail? Thanks, Tina
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.
Hi Jeff, In what version of 5.9 did you encounter this issue? Thanks, Tina
I believe I found it on an appliance which is now at 5.9.2, but well could have been before that upgrade happened.
*** This bug has been marked as a duplicate of bug 1468635 ***