Closed carbonin closed 1 day ago
@carbonin: This pull request references MGMT-18510 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 70.19%. Comparing base (
c5cda7e
) to head (2efed43
). Report is 25 commits behind head on master.
@adriengentil can you take a look at this one when you get a chance?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: adriengentil, carbonin
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD 48d04f6ad16616f0639bc28780842dc689715e18 and 2 for PR HEAD 2efed43109c4e3c1bd5713790e73980efe1cfa3e in total
@carbonin: all tests passed!
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
Distgit: ose-agent-installer-api-server This PR has been included in build ose-agent-installer-api-server-container-v4.18.0-202409120210.p0.gf2f02f5.assembly.stream.el9. All builds following this will include this PR.
Currently when a hub cluster is dual-stack the only way the preprovisioning image controller can determine which callback IP family to provide to the ironic agent is to use the cluster reference in the infraenv. If there is no cluster reference (for late binding cases) then the controller always provides the primary IP family of the hub cluster.
This prevents users from using late-binding to deploy ipv6 only hosts from an ipv4-primary dual-stack hub (or vice versa).
This commit adds an annotation on the infraenv that can be used to override the ip family used when discovering hosts with a particular discovery image.
infraenv.agent-install.openshift.io/ip-family
can be set tov4
,v6
, orv4,v6
to indicate to the controller which family should be used.In newer OCP versions the ironic agent supports multiple callback URLs in its config, but the infrastructure-operator still supports running on hubs that don't have this change so this annotation is still required for those situations.
List all the issues related to this PR
Partially resolves https://issues.redhat.com/browse/MGMT-18510
What environments does this code impact?
How was this code tested?
Unit tests only - I don't have a dual-stack hub cluster to test this on
Checklist
docs
, README, etc) - docs addedReviewers Checklist