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 check for ironic capacity in 'deleting' state #1259
🐛 Don't check for ironic capacity in 'deleting' state #1259
Conversation
Ironic doesn't do any work to speak of in the host's 'deleting' state. It appears this was added (in c3c2c88) due to confusion between ironic's 'deleting' (i.e. the 'deprovisioning' state in Metal³) and Metal³'s 'deleting' state. A result of this was that hosts in the 'unmanaged' state could not be deleted, because by definition they do not have BMC credentials, but the check for Ironic capacity required them. Since unmanaged hosts do not go through 'deprovisioning', removing this unnecessary check from the 'deleting' state should be enough to allow them to be deleted again.
/cc @dtantsur |
/test-centos-e2e-integration-main |
/lgtm |
/test-centos-e2e-integration-main |
/assign @andfasano |
This is no longer needed now that we don't wait for provisioner capacity when going from deprovisioning->deleting.
/test-centos-e2e-integration-main |
1 similar comment
/test-centos-e2e-integration-main |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur 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 |
🐛 Don't check for ironic capacity in 'deleting' state (cherry picked from commit e59dd39)
Ironic doesn't do any work to speak of in the host's 'deleting' state. It appears this was added (in c3c2c88) due to confusion between ironic's 'deleting' (i.e. the 'deprovisioning' state in Metal³) and Metal³'s 'deleting' state.
A result of this was that hosts in the 'unmanaged' state could not be deleted, because by definition they do not have BMC credentials, but the check for Ironic capacity required them. Since unmanaged hosts do not go through 'deprovisioning', removing this unnecessary check from the 'deleting' state should be enough to allow them to be deleted again.