-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Skip errors when unregistering juju kubernetes-workers #48144
Skip errors when unregistering juju kubernetes-workers #48144
Conversation
Hi @ktsakalozos. 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 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. I understand the commands that are listed here. |
/ok-to-test |
if os.path.isfile(kubeconfig_path): | ||
kubectl('delete', 'node', gethostname()) | ||
except CalledProcessError: | ||
hookenv.log('Failed to get unregister node.') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Failed to get/Failed to/
/retest |
4fe950c
to
63e2f37
Compare
63e2f37
to
90a5793
Compare
/assign @Cynerva |
/lgtm Looks good, thanks @ktsakalozos 👍 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cynerva, ktsakalozos Associated issue requirement bypassed by: Cynerva The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 48399, 48450, 48144) |
What this PR does / why we need it: When removing a kubernetes node from using Juju and for some reason kubernetes master fails we should not error the node, instead we should proceed with the removal of the node and the master will recognise that node as unavailable because it will fail heartbeats.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/300Special notes for your reviewer:
Release note: