OCPBUGS-82039: Fix DCM ingress tests to support IPv6-only clusters

[mkowalski]

Replace hardcoded 127.0.0.1 loopback address with dynamic detection based on the router pod's IP family. On IPv6-only clusters, 127.0.0.1 is unavailable, so ::1 must be used instead. Also bracket the IPv6 address in the metrics curl URL via exutil.IPUrl().

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9f758e80-6908-42f9-ad4a-d1e6ce076091

📥 Commits

Reviewing files that changed from the base of the PR and between f183253 and 6833ac3.

📒 Files selected for processing (1)

• test/extended/router/config_manager_ingress.go

---

Walkthrough

This change adds IPv-family-aware loopback address selection for a router exec pod, automatically choosing between 127.0.0.1 and ::1 based on the pod's detected IP address family. The metrics-curl command is updated to use exutil.IPUrl() for proper IP address formatting in curl's --resolve target.

Changes

Cohort / File(s)	Summary
IPv-family-aware loopback selection test/extended/router/config_manager_ingress.go	Added conditional logic to detect IPv6 pods via Status.PodIP inspection and assign the appropriate loopback address (IPv4: 127.0.0.1, IPv6: ::1) to execPod.ipAddress. Updated metrics-curl command construction to wrap the IP address with exutil.IPUrl() for correct --resolve target formatting when querying HAProxy metrics at :1936/metrics.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mkowalski]

/payload e2e-metal-ipi-ovn-ipv6-techpreview

[openshift-ci]

@mkowalski: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[mkowalski]

/payload-job e2e-metal-ipi-ovn-ipv6-techpreview

[openshift-ci]

@mkowalski: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/024ae290-3284-11f1-9472-ab680068a736-0

[openshift-ci-robot]

@mkowalski: This pull request references Jira Issue OCPBUGS-82039, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

Replace hardcoded 127.0.0.1 loopback address with dynamic detection based on the router pod's IP family. On IPv6-only clusters, 127.0.0.1 is unavailable, so ::1 must be used instead. Also bracket the IPv6 address in the metrics curl URL via exutil.IPUrl().

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.

[mkowalski]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

/jira refresh

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.

[jcmoraisjr]

/approve

[gcs278]

Preemptively assigning Joao since you will have the most context here:
/assign @jcmoraisjr

[gcs278]

And I'll keep an eye on this:
/assign @gcs278

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[gcs278]

e2e-metal-ipi-ovn-ipv6-techpreview is passing, which tells me this is the correct fix.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gcs278, jcmoraisjr, mkowalski

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:

• test/extended/router/OWNERS [gcs278,jcmoraisjr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gcs278]

Unrelated failures
/retest

[jcmoraisjr]

/test e2e-gcp-ovn

[openshift-trt]

Job Failure Risk Analysis for sha: 6833ac3

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6	Low [Jira:Node][sig-node] Node non-cnv swap configuration should reject user override of swap settings via KubeletConfig API [OCP-86395] [Suite:openshift/conformance/parallel] This test has passed 31.82% of 330 runs on release 5.0 [Overall] in the last week.
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi	Low [Jira:Node][sig-node] Node non-cnv swap configuration should reject user override of swap settings via KubeletConfig API [OCP-86395] [Suite:openshift/conformance/parallel] This test has passed 31.82% of 330 runs on release 5.0 [Overall] in the last week.

[ShudiLi]

/verified by e2e

[openshift-ci-robot]

@ShudiLi: This PR has been marked as verified by e2e.

Details

In response to this:

/verified by e2e

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]

@mkowalski: 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.

[openshift-ci-robot]

@mkowalski: Jira Issue Verification Checks: Jira Issue OCPBUGS-82039
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-82039 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Replace hardcoded 127.0.0.1 loopback address with dynamic detection based on the router pod's IP family. On IPv6-only clusters, 127.0.0.1 is unavailable, so ::1 must be used instead. Also bracket the IPv6 address in the metrics curl URL via exutil.IPUrl().

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.

[lihongan]

/jira refresh

[openshift-ci-robot]

@lihongan: Jira Issue OCPBUGS-82039 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

Details

In response to this:

/jira refresh

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.