-
Notifications
You must be signed in to change notification settings - Fork 98
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
Upgrade not running to completion when changing OS image #44
Comments
Removing previous log comments and adding new ones with more controllers.
|
capi-controller-manager-6b584cb4b7-wb6vv.log
|
capi-kubeadm-bootstrap-controller-manager-689678664d-vrp4f.log
|
capi-kubeadm-control-plane-controller-manager-57bcb55696-jwkj2.log
|
capm3-controller-manager-8d8dd9f68-7cxww.log
|
baremetal-operator.log
|
In the above logs, some repeating logs are removed for brevity. |
Open bugs that seem to impact this issue: |
This issue is reproduced with k8s version upgrade as well. And, this is not related to the earlier block issue. Gathering more information. |
This issue was caused by VIP not migrating to the control plane node. That made both old and new control plane nodes none responsive. |
What steps did you take and what happened:
kubectl create -f ....
the
infrastructureTemplate.name
to that of the new name you used.Then, wait for the Provisioning of a new node and the de-Provisioning of the
existing one.
However,
What did you expect to happen:
That a new node with the new OS image is Provisioned, and
That the existing node is de-provisioned.
Anything else you would like to add:
I have created a similar issue in CAPI, here
It seems that it is already fixed on the CAPI side and it could be the provider components that are the cause.
Environment:
/kind bug
The text was updated successfully, but these errors were encountered: