Skip to content

[release-1.30] Backport fix for IPv6 single-stack PIP checks#10539

Open
anndono wants to merge 1 commit into
kubernetes-sigs:release-1.30from
anndono:chengan/backport-ipv6-single-stack-pip-fix-to-1.30
Open

[release-1.30] Backport fix for IPv6 single-stack PIP checks#10539
anndono wants to merge 1 commit into
kubernetes-sigs:release-1.30from
anndono:chengan/backport-ipv6-single-stack-pip-fix-to-1.30

Conversation

@anndono

@anndono anndono commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind bug

What this PR does / why we need it:

Cherry-pick the commit fix: Consider ipv6 single stack case when checking pip name and pip prefix id to branch release-1.30.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jun 16, 2026
@github-actions github-actions Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 16, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anndono

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:

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

@k8s-ci-robot k8s-ci-robot requested review from jwtty and nilo19 June 16, 2026 01:40
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 16, 2026
@anndono

anndono commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@anndono anndono force-pushed the chengan/backport-ipv6-single-stack-pip-fix-to-1.30 branch from 362bf31 to 7326748 Compare June 16, 2026 04:57
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

@anndono: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cloud-provider-azure-e2e-ccm-ipv6-vmss-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-ipv6-vmss-capz-1-30
pull-cloud-provider-azure-e2e-ccm-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-capz-1-30
pull-cloud-provider-azure-e2e-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-capz-1-30
pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-vmss-multi-slb-capz-1-30
pull-cloud-provider-azure-e2e-ccm-dualstack-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-dualstack-capz-1-30
pull-cloud-provider-azure-e2e-ccm-ipv6-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-ipv6-capz-1-30
pull-cloud-provider-azure-e2e-ccm-dualstack-vmss-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-dualstack-vmss-capz-1-30
pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-vmss-ip-lb-capz-1-30
pull-cloud-provider-azure-e2e-ccm-vmss-capz-1-30 7326748 link true /test pull-cloud-provider-azure-e2e-ccm-vmss-capz-1-30

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants