| Summary: | [ocp-on-osp] Failed stack can't be deleted successfully | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gan Huang <ghuang> |
| Component: | Installer | Assignee: | Tomas Sedovic <tsedovic> |
| Status: | CLOSED WONTFIX | QA Contact: | Gan Huang <ghuang> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, ghuang, jokerman, mmccomas, rcook, scollier, weshi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| 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-02-22 14:45:54 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: | |
|
Description
Gan Huang
2016-09-29 10:54:29 UTC
Raise severity to "hight" as it would cost much time to release the OpenStack resources for many failed stacks by above workaround. CREATE_FAILED state should not be a blocker for successful stack-delete in most cases (except few exceptions), I need more info how this can be reproduced or what are symptoms. Yeah, the failed stacks which are failed at the part of ansible playbook can be deleted successfully. The failed stacks which can't be deleted successfully were mainly caused by bugs or incorrect usages. Bugs: eg: https://bugzilla.redhat.com/show_bug.cgi?id=1382932 Incorrect usages: This is easy to encounter as QE need test aganist different configs, and we're not familer with all the features so that we usually use some incorrect parameters. If you can't reproduce by BZ1382932, I'll give you a more stable way to reproduce it once I experience it again. Fixed in this upstream PR: https://github.com/redhat-openstack/openshift-on-openstack/pull/274 Can delete failure stack with command "heat stack-delete". Version-Release number of selected component: openshift-on-openstack-0.9.2-1.el7.centos.noarch [root@local-vm ocp-on-osp(bos)]# heat stack-delete weshi-stack Re-open this bug as I experienced this issue frequently in v0.9.5 && v0.9.4 E.g: The stack was failed due to "Create timed out ", then it can't be deleted successfully. $ heat resource-list -n 2 e3843b38-cc04-4334-b0a3-d71527f32566|grep PRO | openshift_nodes | 3613b493-605c-4dc8-82d6-1ef17022b9c0 | OS::Heat::AutoScalingGroup | DELETE_IN_PROGRESS | 2016-11-02T01:57:33 | ghuang-bug | | init | ab25b91a-cb78-4610-b805-2f226676b9b5 | OS::Heat::MultipartMime | DELETE_IN_PROGRESS | 2016-11-02T02:29:53 | ghuang-bug-openshift_nodes-6jbbltfv7idt-rmy4y544uskl-r3ykemfjfshp | | internal_port | bb3ac358-77f1-4ad9-8ba8-feaea2cd02d2 | OOShift::ContainerPort | DELETE_IN_PROGRESS | 2016-11-02T02:29:53 | ghuang-bug-openshift_nodes-6jbbltfv7idt-rmy4y544uskl-r3ykemfjfshp | | port | c1198769-059f-45ec-99b5-857540b7f11a | OS::Neutron::Port | DELETE_IN_PROGRESS | 2016-11-02T02:29:54 | ghuang-bug-openshift_nodes-6jbbltfv7idt-rmy4y544uskl-r3ykemfjfshp | Sorry, please ignore the output for "heat resource-list -n 2" in comment 6 Please refer to: http://pastebin.test.redhat.com/426022 Reduce the severity and priority as currently I can increase timeout when creating the stack to workaround it. Team, Closing this as the heat templates have been deprecated. Future funcionality and integration capabilities will be moving to openshift-ansible moving forward. |