Skip to content
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.

Final control plane node can never be deleted #109

Closed
liztio opened this issue Jul 24, 2019 · 2 comments · Fixed by #205
Closed

Final control plane node can never be deleted #109

liztio opened this issue Jul 24, 2019 · 2 comments · Fixed by #205
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@liztio
Copy link
Contributor

liztio commented Jul 24, 2019

/kind bug

What steps did you take and what happened:

  1. Create a kind management cluster
  2. create a capa cluster using capd
  3. delete the capd cluster (using the changes in [0.1] Delete machines kubernetes-sigs/cluster-api#1180 so the machines get deleted first)
  4. Control plane node fails to delete with an error like failed with exit code one

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

The cluster will try to find another control-plane node to run kubectl on, but of course no such container exists. It will therefore try to execute a command on a container with the name of the empty string, which doesn't exist.

Environment:

  • Cluster-api-provider-docker version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 24, 2019
@chuckha
Copy link
Contributor

chuckha commented Jul 25, 2019

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 25, 2019
@chuckha
Copy link
Contributor

chuckha commented Aug 20, 2019

/assign
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Aug 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants