-
Notifications
You must be signed in to change notification settings - Fork 261
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 deprovision provisioned host due to error #916
Don't deprovision provisioned host due to error #916
Conversation
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hardys 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 |
Adding a test to cover this would be good, but otherwise lgtm, thanks! |
During provisioning, we want an error to cause the Host to be deprovisioned again, but we very much do not want that to happen when the Host is already provisioned. Due to an error in 0a7713b, provisioned Hosts were being automatically deprovisioned whenever an error (other than a registration error) occurred. In practice this only manifested on Adopt() failures, since we don't yet report power management failures. Fixes metal3-io#915
318850a
to
c15f0d8
Compare
Added a test. |
/lgtm |
@sadasu: adding LGTM is restricted to approvers and reviewers in OWNERS files. 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. |
/lgtm |
During provisioning, we want an error to cause the Host to be
deprovisioned again, but we very much do not want that to happen when
the Host is already provisioned. Due to an error in
0a7713b, provisioned Hosts were being
automatically deprovisioned whenever an error (other than a registration
error) occurred.
In practice this only manifested on Adopt() failures, since we don't yet
report power management failures.
Fixes #915