Skip to content

Conversation

@elfosardo
Copy link

When deprovisioning a host with automated cleaning enabled, BMO now:

  1. Checks if a PreprovisioningImage is available before proceeding (in the provisioner's configureNode function)
  2. Treats a PPI with a DeletionTimestamp as unavailable (in the controller's getPreprovImage function)

Previously, the StateDeprovisioning case was not handled, and PPIs being deleted could still be used. This caused Ironic to fall back to building its own ISO and fail with a misleading "uefi_esp.img not found" error when the PPI was unavailable or being deleted.

Assisted-By: Claude Sonnet 4.5 (commercial license)

(cherry picked from commit c4631b5)

When deprovisioning a host with automated cleaning enabled, BMO now:

1. Checks if a PreprovisioningImage is available before proceeding
   (in the provisioner's configureNode function)
2. Treats a PPI with a DeletionTimestamp as unavailable
   (in the controller's getPreprovImage function)

Previously, the StateDeprovisioning case was not handled, and PPIs
being deleted could still be used. This caused Ironic to fall back
to building its own ISO and fail with a misleading "uefi_esp.img
not found" error when the PPI was unavailable or being deleted.

Assisted-By: Claude Sonnet 4.5 (commercial license)

Signed-off-by: Riccardo Pittau <elfosardo@gmail.com>
(cherry picked from commit c4631b5)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 29, 2025
@openshift-ci-robot
Copy link

@elfosardo: This pull request references Jira Issue OCPBUGS-67294, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-67275 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-67275 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @jadhaj

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

When deprovisioning a host with automated cleaning enabled, BMO now:

  1. Checks if a PreprovisioningImage is available before proceeding (in the provisioner's configureNode function)
  2. Treats a PPI with a DeletionTimestamp as unavailable (in the controller's getPreprovImage function)

Previously, the StateDeprovisioning case was not handled, and PPIs being deleted could still be used. This caused Ironic to fall back to building its own ISO and fail with a misleading "uefi_esp.img not found" error when the PPI was unavailable or being deleted.

Assisted-By: Claude Sonnet 4.5 (commercial license)

(cherry picked from commit c4631b5)

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Dec 29, 2025
@openshift-ci openshift-ci bot requested a review from jadhaj December 29, 2025 10:34
@elfosardo
Copy link
Author

/cherry-pick release-4.20

@openshift-ci openshift-ci bot requested review from honza and iurygregory December 29, 2025 10:34
@openshift-ci
Copy link

openshift-ci bot commented Dec 29, 2025

[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

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 29, 2025
@openshift-cherrypick-robot

@elfosardo: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.20

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-sigs/prow repository.

@elfosardo
Copy link
Author

/override ci/prow/okd-scos-images

@openshift-ci
Copy link

openshift-ci bot commented Dec 29, 2025

@elfosardo: Overrode contexts on behalf of elfosardo: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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-sigs/prow repository.

@elfosardo
Copy link
Author

/override ci/prow/okd-scos-images

@openshift-ci
Copy link

openshift-ci bot commented Dec 30, 2025

@elfosardo: Overrode contexts on behalf of elfosardo: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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-sigs/prow repository.

@openshift-ci
Copy link

openshift-ci bot commented Dec 30, 2025

@elfosardo: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants