[release-5.0] OCPBUGS-127501: Backport openshift-ci env and artifact improvements

[ajaggapa]

Is this a BUG FIX or a FEATURE ?:

/kind cleanup

What this PR does / why we need it:

Backports the following OpenShift CI improvements from main to release-5.0.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-127501

• #299 — Openshift CI: env setup for dualstack tests
  Adds an nthhost helper in openshift-ci/common.sh that returns the Nth host in a CIDR via Python's ipaddress.ip_network. For IP_STACK=v4v6, derives PROVISIONING_HOST_EXTERNAL_IPV6 from EXTERNAL_SUBNET_V6 (host index 1) instead of a hardcoded dummy address.

• #300 — openshift ci: improve junit file and artifact collection for e2etests
  Sets REPORTER_PATH from ARTIFACT_DIR so artifacts land in the standard OpenShift CI location. Passes --junit-report and --export directly to ginkgo for iBGP and eBGP test runs, writing results to separate ibgp/ and ebgp/ subdirectories. Both runs execute even if one fails, and the script exits non-zero if either run failed. Skips kind log export when running against an external kubeconfig.

Special notes for your reviewer:

Both commits cherry-picked cleanly from main with no conflicts. These are CI/tooling-only changes — no functional MetalLB behavior is modified.

Release note:

NONE

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: fb315afe-b2e7-491e-97f5-f7c45404ba70

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[ajaggapa]

/retest

[ajaggapa]

/test metallb-e2e-metal

[fedepaol]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ajaggapa, fedepaol

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:

• OWNERS [fedepaol]

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

[ajaggapa]

/label backport-risk-assessed

[openshift-ci]

@ajaggapa: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

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.

[ajaggapa]

/verified by ci

[openshift-ci-robot]

@ajaggapa: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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.

[fedepaol]

/label backport-risk-assessed

[openshift-ci-robot]

@ajaggapa: This pull request references Jira Issue OCPBUGS-127501, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-127501 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Is this a BUG FIX or a FEATURE ?:

/kind cleanup

What this PR does / why we need it:

Backports the following OpenShift CI improvements from main to release-5.0.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-127501

• #299 — Openshift CI: env setup for dualstack tests
  Adds an nthhost helper in openshift-ci/common.sh that returns the Nth host in a CIDR via Python's ipaddress.ip_network. For IP_STACK=v4v6, derives PROVISIONING_HOST_EXTERNAL_IPV6 from EXTERNAL_SUBNET_V6 (host index 1) instead of a hardcoded dummy address.

• #300 — openshift ci: improve junit file and artifact collection for e2etests
  Sets REPORTER_PATH from ARTIFACT_DIR so artifacts land in the standard OpenShift CI location. Passes --junit-report and --export directly to ginkgo for iBGP and eBGP test runs, writing results to separate ibgp/ and ebgp/ subdirectories. Both runs execute even if one fails, and the script exits non-zero if either run failed. Skips kind log export when running against an external kubeconfig.

Special notes for your reviewer:

Both commits cherry-picked cleanly from main with no conflicts. These are CI/tooling-only changes — no functional MetalLB behavior is modified.

Release note:

NONE

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.

[ajaggapa]

/jira refresh

[openshift-ci-robot]

@ajaggapa: This pull request references Jira Issue OCPBUGS-127501, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-127501 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

[ajaggapa]

/jira refresh

[openshift-ci-robot]

@ajaggapa: This pull request references Jira Issue OCPBUGS-127501, which is invalid:

• expected Jira Issue OCPBUGS-127501 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

[ajaggapa]

/jira refresh

[openshift-ci-robot]

@ajaggapa: This pull request references Jira Issue OCPBUGS-127501, which is invalid:

• expected Jira Issue OCPBUGS-127501 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

[ajaggapa]

/jira refresh

[openshift-ci-robot]

@ajaggapa: This pull request references Jira Issue OCPBUGS-127501, 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 (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-127503 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-127503 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
• bug has dependents

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.

[openshift-ci]

@ajaggapa: 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]

@ajaggapa: Jira Issue OCPBUGS-127501: All pull requests linked via external trackers have merged:

• openshift/metallb#303

All linked pull requests have the verified tag. Jira Issue OCPBUGS-127501 has been moved to the VERIFIED state.

Details

In response to this:

Is this a BUG FIX or a FEATURE ?:

/kind cleanup

What this PR does / why we need it:

Backports the following OpenShift CI improvements from main to release-5.0.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-127501

• #299 — Openshift CI: env setup for dualstack tests
  Adds an nthhost helper in openshift-ci/common.sh that returns the Nth host in a CIDR via Python's ipaddress.ip_network. For IP_STACK=v4v6, derives PROVISIONING_HOST_EXTERNAL_IPV6 from EXTERNAL_SUBNET_V6 (host index 1) instead of a hardcoded dummy address.

• #300 — openshift ci: improve junit file and artifact collection for e2etests
  Sets REPORTER_PATH from ARTIFACT_DIR so artifacts land in the standard OpenShift CI location. Passes --junit-report and --export directly to ginkgo for iBGP and eBGP test runs, writing results to separate ibgp/ and ebgp/ subdirectories. Both runs execute even if one fails, and the script exits non-zero if either run failed. Skips kind log export when running against an external kubeconfig.

Special notes for your reviewer:

Both commits cherry-picked cleanly from main with no conflicts. These are CI/tooling-only changes — no functional MetalLB behavior is modified.

Release note:

NONE

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.