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 immediately retry on Inspect fail #840

Merged
merged 2 commits into from
Mar 31, 2021

Conversation

zaneb
Copy link
Member

@zaneb zaneb commented Mar 30, 2021

Ensure that if the ironic node enters the InspectFail state, we not only report the error but also wait until after the exponential backoff before retrying, instead of retrying immediately.

The previous attempt to fix this in 2d02462 didn't take due to a missing return.

@metal3-io-bot metal3-io-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 30, 2021
@zaneb zaneb requested a review from s3rj1k March 30, 2021 16:56
@s3rj1k
Copy link
Member

s3rj1k commented Mar 30, 2021

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: s3rj1k, zaneb

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

In the patch 2d02462 we were supposed
to report an error and wait for an exponentially increasing backoff time
before retrying. However, due to a missing early return, we are retrying
immediately with the result that the error gets cleared in fairly short
order.

Return early on failure as intended. Also, use the operationFailed()
convenience function instead of ad hoc updates to the return variables;
this case was likely missed due to the lack of a return.
@metal3-io-bot metal3-io-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 30, 2021
@zaneb zaneb requested a review from andfasano March 30, 2021 18:20
@zaneb
Copy link
Member Author

zaneb commented Mar 30, 2021

/test-integration

@andfasano
Copy link
Member

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 31, 2021
@metal3-io-bot metal3-io-bot merged commit f007ef9 into metal3-io:master Mar 31, 2021
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. lgtm Indicates that a PR is ready to be merged. 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.

None yet

4 participants