OCPBUGS-85824: Fix empty IRONIC_BASE_URL#603
Conversation
When the `apiServerInternalIPs`is an empty list in the Infrastructure CR, the `GetIronicIPs`failed to fall back to use the metal3 pod IP. This caused the metal3-image-customization to be createdy with empty `IRONIC_BASE_URL`, resulting in the following error in the `PreprovisioningImage` CR: 'Could not add ironic agent to image: ironicBaseURL is required' The problem was that `GetIronicIPs` did not account for empty list. Assisted-By: Claude 4.6 Opus High Signed-off-by: Iury Gregory Melo Ferreira <imelofer@redhat.com>
|
@iurygregory: This pull request references Jira Issue OCPBUGS-85824, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
WalkthroughThis PR fixes a fallback condition in ChangesGetIronicIPs Empty Slice Fallback
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@iurygregory: This pull request references Jira Issue OCPBUGS-85824, which is valid. 3 validation(s) were run on this bug
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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur, iurygregory 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 |
|
/test e2e-agnostic-ovn |
|
/lgtm |
|
/verified later @sgoveas |
|
@sgoveas: This PR has been marked to be verified later by 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. |
|
@iurygregory: all tests passed! 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. |
|
@iurygregory: Jira Issue OCPBUGS-85824: All pull requests linked via external trackers have merged: This pull request has the 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. |
|
/cherry-pick release-4.22 |
|
@iurygregory: new pull request created: #606 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 kubernetes-sigs/prow repository. |
|
Fix included in release 5.0.0-0.nightly-2026-05-20-101113 |
|
/cherry-pick release-4.21 |
|
@iurygregory: new pull request created: #614 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 kubernetes-sigs/prow repository. |
When the
apiServerInternalIPsis an empty list in the Infrastructure CR, theGetIronicIPsfailed to fall back to use the metal3 pod IP. This caused the metal3-image-customization to be createdy with emptyIRONIC_BASE_URL, resulting in the following error in thePreprovisioningImageCR:'Could not add ironic agent to image: ironicBaseURL is required'
The problem was that
GetIronicIPsdid not account for empty list.Assisted-By: Claude 4.6 Opus High
Summary by CodeRabbit
Bug Fixes
Tests