Bug 1565418
Summary: | Service retirement does not properly handle retiring orchestration stacks | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Jeff Warnica <jwarnica> |
Component: | Automate | Assignee: | Tina Fitzgerald <tfitzger> |
Status: | CLOSED DUPLICATE | QA Contact: | Dave Johnson <dajohnso> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.9.0 | CC: | 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
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 *** |