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
Controller manager failed to be started when rollback from v1.8.3 to v1.7.3 #56574
Comments
/sig apps |
Was the controller manager rolled back as well? |
@liggitt Yes. I have rolled back all apiserver, controller manager, scheduler, kube-proxy and kubelet services back to v1.7.3 |
Should I restore ETCD data before roll back to v1.7.3 |
What is the output of kubectl version |
Enables the v1beta2 version of the apps API group by default #50643 Seems group version is not enabled in 1.7.3 |
|
Ah. Setup/cleanup of APIService objects between versions had a bug (#51912) that was resolved in 1.7.6 and 1.8 I would recommending targeting the latest 1.7.x release for the downgrade. |
Thanks @liggitt |
Hi liqlin2015, I also got this problem while rollback k8s v1.8.4 to 1.7.4 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
I had a kubernetes v1.8.3 cluster setup and running fine. Then I rollback kubernetes core services apiserver, controller-manager and scheduler to v1.7.3 for some verification.
However controller manager can not be started due to following error
What you expected to happen:
Kubernetes core services apiserver, controler manager and scheduler should be started successfully in the rollback case.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment: None
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: