-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Stuck on replacing controlplane nodes #3127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I checkout the issue a bit deeper and seems the cloud controller in the provision cluster is unable to set the providerID. I think it would helpful to improve the log message. |
Makes sense to improve the error message, +1 /milestone v0.3.x |
/help |
@vincepri: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v0.4.0 |
Let's switch to a condition / reason message for Ready to present this information to users, this will be fixed in #3138 /close |
@vincepri: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What steps did you take and what happened:
Waiting for control plane to pass control plane health check to continue reconciliation: control plane machine namespace/node-cp-v2-s8p8w has no status.nodeRef
What did you expect to happen:
Anything else you would like to add:
logs of capi-controller-manager
I would like to help. I already opened the issue on provider side. I wasn't sure were to open it. kubernetes-sigs/cluster-api-provider-vsphere#921.
Environment:
kubectl version
):/etc/os-release
): ubuntu 18.04/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: