Skip to content

[release-4.21] UPSTREAM: <carry>: OCPBUGS-99230: Fix ClusterIsIPv6() detection for dual-stack v6-primary clusters#2722

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-2603-to-release-4.21
Open

[release-4.21] UPSTREAM: <carry>: OCPBUGS-99230: Fix ClusterIsIPv6() detection for dual-stack v6-primary clusters#2722
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-2603-to-release-4.21

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #2603

/assign jluhrsen


…imary clusters

  Detect cluster's primary IP family by querying kubernetes.default service
  ClusterIP instead of using HasIPv4/HasIPv6 flags. The previous logic
  incorrectly returned ipv4 for dual-stack v6-primary clusters because
  both HasIPv4 and HasIPv6 were true.

  This matches the upstream approach in test/e2e/e2e.go and fixes DNS tests
  that were querying for A records instead of AAAA records in v6-primary
  environments.
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

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: Enterprise

Run ID: 6b73eeeb-5ef2-4fa0-aa49-28288713c474

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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-39360 has been cloned as Jira Issue OCPBUGS-99230. Will retitle bug to link to clone.
/retitle [release-4.21] UPSTREAM: : OCPBUGS-99230: Fix ClusterIsIPv6() detection for dual-stack v6-primary clusters

Details

In response to this:

This is an automated cherry-pick of #2603

/assign jluhrsen


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 openshift-ci Bot changed the title [release-4.21] UPSTREAM: <carry>: OCPBUGS-39360: Fix ClusterIsIPv6() detection for dual-stack v6-primary clusters [release-4.21] UPSTREAM: <carry>: OCPBUGS-99230: Fix ClusterIsIPv6() detection for dual-stack v6-primary clusters Jul 20, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 20, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-99230, 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 dependent Jira Issue OCPBUGS-39360 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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:

This is an automated cherry-pick of #2603

/assign jluhrsen


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
openshift-ci Bot requested review from benluddy and bertinatto July 20, 2026 19:37
@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign jacobsee for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@jluhrsen

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@jluhrsen: This pull request references Jira Issue OCPBUGS-99230, which is invalid:

  • expected dependent Jira Issue OCPBUGS-39360 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

@jluhrsen

Copy link
Copy Markdown

/retest

@jluhrsen

Copy link
Copy Markdown

/test e2e-openstack-dualstack-v6primary

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown

@jluhrsen: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test artifacts
/test configmap-scale
/test e2e-aws-jenkins
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-crun
/test e2e-aws-ovn-downgrade
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-runc
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test images
/test integration
/test k8s-e2e-conformance-aws
/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/test okd-scos-images
/test perfscale-control-plane-6nodes
/test unit
/test verify
/test verify-commits

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-hpa
/test e2e-aws-ovn
/test e2e-aws-ovn-techpreview
/test e2e-aws-ovn-techpreview-serial-1of2
/test e2e-aws-ovn-techpreview-serial-2of2
/test e2e-aws-single-node
/test e2e-azure
/test e2e-external-aws-ccm
/test e2e-metal-ipi-ovn-dualstack
/test e2e-openstack
/test e2e-openstack-csi-cinder
/test e2e-openstack-csi-manila
/test e2e-vsphere
/test k8s-e2e-aws
/test k8s-e2e-aws-ovn-serial
/test k8s-e2e-gcp-five-control-plane-replicas
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-kubernetes-release-4.21-artifacts
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-crun
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-fips
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-hypershift
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-runc
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-serial-1of2
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-serial-2of2
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-techpreview
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-techpreview-serial-1of2
pull-ci-openshift-kubernetes-release-4.21-e2e-aws-ovn-techpreview-serial-2of2
pull-ci-openshift-kubernetes-release-4.21-e2e-gcp
pull-ci-openshift-kubernetes-release-4.21-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-kubernetes-release-4.21-images
pull-ci-openshift-kubernetes-release-4.21-integration
pull-ci-openshift-kubernetes-release-4.21-k8s-e2e-conformance-aws
pull-ci-openshift-kubernetes-release-4.21-k8s-e2e-gcp-ovn
pull-ci-openshift-kubernetes-release-4.21-k8s-e2e-gcp-serial
pull-ci-openshift-kubernetes-release-4.21-okd-scos-images
pull-ci-openshift-kubernetes-release-4.21-unit
pull-ci-openshift-kubernetes-release-4.21-verify
pull-ci-openshift-kubernetes-release-4.21-verify-commits
Details

In response to this:

/test e2e-openstack-dualstack-v6primary

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

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-crun 6a77183 link true /test e2e-aws-ovn-crun

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

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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