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

Validate cluster after updating bastions #8074

Merged
merged 2 commits into from
Dec 10, 2019

Conversation

johngmyers
Copy link
Member

/kind bug

The fix #7872 exposed an issue where rolling update starts updating the first master before the terminated bastion is replaced by the ASG. Before that fix, kops was relying on the fact that the resulting validation failure was ignored.

This fixes the issue by waiting for validation to succeed after terminating a bastion. It does not change the behavior of updating the first bastion without validating the cluster.

The other possible fix would be to make validation ignore any shortfall in members of bastion instance groups.

Fixes #8070

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 10, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @johngmyers. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 10, 2019
@rifelpet
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 10, 2019
@johngmyers
Copy link
Member Author

/test pull-kops-e2e-kubernetes-aws

Copy link
Member

@zetaab zetaab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @johngmyers for fixing this!

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 10, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, zetaab

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 10, 2019
@zetaab
Copy link
Member

zetaab commented Dec 10, 2019

@johngmyers could you please cherry-pick this to release-1.17 as it is "broken" there

@k8s-ci-robot k8s-ci-robot merged commit e2060cd into kubernetes:master Dec 10, 2019
@johngmyers johngmyers deleted the validate-bastion branch December 10, 2019 16:06
@johngmyers
Copy link
Member Author

Is there a procedure for cherry picking other than just raising a PR?

@zetaab
Copy link
Member

zetaab commented Dec 10, 2019

at least i am not aware of any other

@rifelpet
Copy link
Member

Theres a convenient script for cherry picking that is documented here

k8s-ci-robot added a commit that referenced this pull request Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rolling-update does not validate cluster correctly after bastion
4 participants