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

Don't wait for Host deprovisioning to delete Machine #57

Closed
wants to merge 1 commit into from

Conversation

zaneb
Copy link
Member

@zaneb zaneb commented Mar 12, 2020

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

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Mar 12, 2020
@openshift-ci-robot
Copy link

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 /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.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 12, 2020
@zaneb
Copy link
Member Author

zaneb commented Mar 12, 2020

/assign @mhrivnak
/cc @rwsu

Copy link

@rwsu rwsu left a 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.

pkg/cloud/baremetal/actuators/machine/actuator_test.go Outdated Show resolved Hide resolved
pkg/cloud/baremetal/actuators/machine/actuator_test.go Outdated Show resolved Hide resolved
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
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: zaneb
To complete the pull request process, please assign mhrivnak
You can assign the PR to them by writing /assign @mhrivnak in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mhrivnak
Copy link
Member

/ok-to-test

@openshift-ci-robot openshift-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 Apr 28, 2020
@mhrivnak
Copy link
Member

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.

@openshift-ci-robot
Copy link

@zaneb: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-metal-ipi 4eaa2b8 link /test e2e-metal-ipi

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.

@dhellmann
Copy link

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.

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).

@dhellmann
Copy link

See #87

@zaneb
Copy link
Member Author

zaneb commented Aug 22, 2020

I'm working on a more comprehensive solution to the problem, so closing this.
/close

@openshift-ci-robot
Copy link

@zaneb: Closed this PR.

In response to this:

I'm working on a more comprehensive solution to the problem, so closing this.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

Deleting a Host doesn't immediately affect Machine
5 participants