kubernetes / kubernetes/cloud-provider-openstack
Node is not deleted from the cluster, after being deleted from openstack
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 720
- Forks
- 687
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 51
Description
/kind bug
What happened:
When deleting a baremetal node from openstack, occm doesn't detect the deletion, and the node remains in the cluster as NotReady.
The logs say: error checking if node <node-name> exists: failed to find object
What you expected to happen:
I expect to see a log line that the node was deleted, and then for the node to not be in the cluster anymore.
Anything else we need to know?:
It seems this is the same issue reported in: https://github.com/kubernetes/cloud-provider-openstack/issues/2999
I tried the PR proposed in the ticket (https://github.com/nokia/cloud-provider-openstack/pull/1/changes), and it fixed the issue for us.
Environment:
- openstack-cloud-controller-manager version: v1.35.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the openstack-cloud-controller-manager node deletion path and the logs showing “failed to find object.” Compare the behavior with issue #2999 and the referenced PR changes, then reproduce deletion of a baremetal node in OpenStack. Done means the controller logs the deletion and the node disappears from the cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100