Bug 1575572
Summary: | Can't remove an overcloud node with wrong network configuration (not accessible) | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Eduard Barrera <ebarrera> |
Component: | openstack-tripleo | Assignee: | James Slagle <jslagle> |
Status: | CLOSED NOTABUG | QA Contact: | Arik Chernetsky <achernet> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 11.0 (Ocata) | CC: | aschultz, bfournie, dtantsur, ebarrera, hjensas, mburns |
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-06-06 11:56:29 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
Eduard Barrera
2018-05-07 10:24:27 UTC
Hi! It's hard to tell what went wrong from a quick glance, but http://tripleo.org/install/troubleshooting/troubleshooting-nodes.html#how-do-i-repair-broken-nodes may be the answer. I don't see signs of problems on the nova/ironic side at the first glance. First, what exactly failure does Heat show? Second, you said you tried 'openstack server delete', what was the result? What was the final state of the nova instance and the ironic node? Hi, So, it's a bit unclear whether the node were deleted and properly cleaned up after they got problematic. Just to be clear on terminology: 1. Ironic node delete ('openstack baremetal node delete') removes it from the inventory completely. 2. Instance delete ('openstack server delete') removes the Nova instance and unprovisions the node. It does not do #1. 3. Overcloud node delete ('openstack overcloud node delete') removes the node from the Heat stack and does #2, but NOT #1! What I hear from you is that #3 fails with not found error, so the node is no longer in the stack. We just have to unprovision it. So, the plan is: 1. Try undeploying instance with 'openstack server delete'. 2. If it fails and you don't understand why, follow http://tripleo.org/install/troubleshooting/troubleshooting-nodes.html#how-do-i-repair-broken-nodes. 3. In both cases wipe the node's hard drive and power it off before doing anything else! Now, as to the warning on that page. Force-deleting a node may prevent Ironic and Nova from cleaning up resources associated with it. Specifically, it will stay powered on and ports won't be disconnected. A left that warning mostly because people used to take this procedure too easily, doing it every time they had a deployment failure. Hope that helps, Dmitry Eduard - based on comments 7 and 8, do you have all the info you need to close this? Eduard - I think the info has been provided, please reopen this if not the case. Thanks. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |