Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Missing VM tags results in failed kubernetes upgrade and scale #3663

Closed
CecileRobertMichon opened this issue Aug 13, 2018 · 4 comments
Closed

Comments

@CecileRobertMichon
Copy link
Contributor

CecileRobertMichon commented Aug 13, 2018

Upgrade and scale should not rely on VM tags to determine k8s version during upgrade as those could easily be removed or modified.

https://github.com/Azure/acs-engine/blob/master/pkg/operations/kubernetesupgrade/upgradecluster.go#L200

https://github.com/Azure/acs-engine/blob/master/cmd/scale.go#L225

@serbrech
Copy link
Member

Any suggestion on how to identify VMs to upgrade without relying on tags? Should it rely on VM names instead?

@CecileRobertMichon CecileRobertMichon changed the title Missing VM tags results in failed kubernetes upgrade Missing VM tags results in failed kubernetes upgrade and scale Sep 4, 2018
@CecileRobertMichon
Copy link
Contributor Author

@serbrech I think for now even a simple check to make sure those tags exist before dereferencing them would help so that we can return a meaningful error ("expected tags "..." and "..." on VM "..." but no tags were found" or something like that) instead of panicking would be better.

@CecileRobertMichon
Copy link
Contributor Author

/assign @mboersma

@mboersma
Copy link
Member

Fixed in #4100.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants