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
Don't wait for Host deprovisioning to delete Machine #57
Conversation
Hi @zaneb. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
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.
I like the optimization of using the deletionTimestamp, instead of waiting for the Deleting state. One suggestion is to change the test case names. Other than that, it looks good to me.
If the Host is marked for deletion, don't wait for deprovisioning to complete (and hence the provisioning status to move to Deleting) before also marking the Machine for deletion. Fixes openshift#56
22917fe
to
4eaa2b8
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zaneb The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
Per my comment on the issue, I don't think this change will fix the described problem. Generally, I'm not seeing how deleting the Machine sooner in the workflow is advantageous. |
@zaneb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Maybe the thing to do is add the appropriate annotation as soon as the host is marked as being deleted, and then actually delete the machine after the host is deprovisioned (if the machineset controller hasn't already started to delete it). |
See #87 |
I'm working on a more comprehensive solution to the problem, so closing this. |
@zaneb: Closed this PR. In response to this:
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. |
If the Host is marked for deletion, don't wait for deprovisioning to
complete (and hence the provisioning status to move to Deleting) before
also marking the Machine for deletion.
Fixes #56