Navigation Menu

Skip to content
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

Unable to upgrade to v1.10 using kubeadm #61794

Closed
rajansandeep opened this issue Mar 27, 2018 · 7 comments
Closed

Unable to upgrade to v1.10 using kubeadm #61794

rajansandeep opened this issue Mar 27, 2018 · 7 comments
Assignees
Labels
area/kubeadm kind/bug Categorizes issue or PR as related to a bug. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@rajansandeep
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
When trying to upgrade kubernetes from v1.9.6 to v1.10.0 using kubeadm, it throws a version error and doesn't upgrade.

# kubeadm upgrade apply v1.10.0
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade/version] You have chosen to change the cluster version to "v1.10.0"
[upgrade/versions] Cluster version: v1.9.6
[upgrade/versions] kubeadm version: v1.9.6
[upgrade/version] FATAL: The --version argument is invalid due to these fatal errors:

	- Specified version to upgrade to "v1.10.0" is at least one minor release higher than the kubeadm minor release (10 > 9). Such an upgrade is not supported

Please fix the misalignments highlighted above and try upgrading again

What you expected to happen:

Successfully upgrade to Kubernetes v1.10.0 via kubeadm

How to reproduce it (as minimally and precisely as possible):

kubeadm upgrade apply v1.10.0

Anything else we need to know?:
This issue may be related to #61764. I raised a separate issue because this seems to be on a broader/general scope.

Environment: baremetal

  • Kubernetes version (use kubectl version):
# kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:21:50Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. kind/bug Categorizes issue or PR as related to a bug. labels Mar 27, 2018
@rajansandeep
Copy link
Contributor Author

/area kubeadm
/sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added area/kubeadm sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 27, 2018
@lareeth
Copy link

lareeth commented Mar 27, 2018

Are you using RPMs? They haven't been updated yet, you need to update kubeadm to the same version you want to upgrade to.

Related: #61763 kubernetes/release#539

If not, download the latest binaries, and replace kubeadm with the latest version. Once upgraded, then replace the rest of the binaries, such as kubectl and kubelet.

@calebamiles
Copy link
Contributor

/assign

@calebamiles
Copy link
Contributor

rpms and debs have been published now, @rajansandeep

cc: @jdumars, @kubernetes/kubernetes-release-managers

@rajansandeep
Copy link
Contributor Author

@calebamiles thank you!
But now, I see that the kubeadm upgrade plan and kubeadm upgrade apply hangs/times-out and is unsuccessful.

# kubeadm upgrade plan
[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster...
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.10.0
[upgrade/versions] kubeadm version: v1.10.0
[upgrade/versions] Latest stable version: v1.10.0

@calebamiles
Copy link
Contributor

Acknowledged, @rajansandeep. I think you the issue you identified is a question better handled by someone in @kubernetes/sig-cluster-lifecycle-bugs. Your issue might be tracked under kubernetes/kubeadm#740; and if so closing this issue will help keep the issue queue a bit more sane. Thanks!

@rajansandeep
Copy link
Contributor Author

Yes, I think the issue you mentioned above covers this issue. Hence closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubeadm kind/bug Categorizes issue or PR as related to a bug. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

4 participants