-
Notifications
You must be signed in to change notification settings - Fork 27
[release-4.21] OCPBUGS-68369: Abort inspection/cleaning before powering off during deletion #449
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
base: release-4.21
Are you sure you want to change the base?
[release-4.21] OCPBUGS-68369: Abort inspection/cleaning before powering off during deletion #449
Conversation
When deleting a host in inspecting or cleaning state, it would get stuck because Ironic rejects power changes while a target provision state is active. This fix detects these states and sends an abort command first, allowing deletion to proceed immediately instead of waiting for inspection/cleaning to complete. Assisted-By: Claude Sonnet 4.5 (commercial license) Signed-off-by: Riccardo Pittau <elfosardo@gmail.com> (cherry picked from commit 4489951)
|
@elfosardo: This pull request references Jira Issue OCPBUGS-68369, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elfosardo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
b2f440d to
6d26883
Compare
|
/hold |
When deleting a BMH during inspection, power-off could hang because: 1. After abort, node is in InspectFail with TargetProvisionState still set, blocking power changes 2. Ironic does not auto-clear TargetProvisionState in InspectFail state 3. PowerOff() misinterpreted the abort message in LastError as a power-off failure Fix by: - Explicitly transitioning from InspectFail to manageable to clear TargetProvisionState and allow power changes - Ignoring "aborted" errors in LastError during power-off (cherry picked from commit 1693931)
6d26883 to
b5655e0
Compare
|
we need #450 |
|
@elfosardo: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Plus Fix deletion hang when aborting inspection during power-off