Skip to content

CORS-4209: ensure NodeIPFamilies field is kept as-is after transforming#426

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
tthvo:CORS-4209
Mar 2, 2026
Merged

CORS-4209: ensure NodeIPFamilies field is kept as-is after transforming#426
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
tthvo:CORS-4209

Conversation

@tthvo
Copy link
Member

@tthvo tthvo commented Oct 28, 2025

In dual-stack environment, the CCM AWS provider expects NodeIPFamilies (kubernetes/cloud-provider-aws#638) to be in the format:

NodeIPFamilies=ipv4
NodeIPFamilies=ipv6

However, iniv1 is serializing go slices as comma-separated list, for example:

NodeIPFamilies=ipv4,ipv6

This commit ensures the original NodeIPFamilies field is kept as-is after transforming.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 28, 2025

@tthvo: This pull request references CORS-4209 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 story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

In dual-stack environment, the CCM AWS provider expects NodeIPFamilies (kubernetes/cloud-provider-aws#638) to be in the format:

NodeIPFamilies=ipv4
NodeIPFamilies=ipv6

However, iniv1 is serializing go slices as comma-separated list, for example:

NodeIPFamilies=ipv4,ipv6

This commit ensures the original NodeIPFamilies field is kept as-is after transforming.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 28, 2025
@tthvo
Copy link
Member Author

tthvo commented Oct 28, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 28, 2025

@tthvo: This pull request references CORS-4209 which is a valid jira issue.

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.

@tthvo
Copy link
Member Author

tthvo commented Oct 28, 2025

/cc @sadasu

@openshift-ci openshift-ci bot requested a review from sadasu October 28, 2025 21:31
@damdo
Copy link
Member

damdo commented Oct 30, 2025

/assign @nrb

@nrb
Copy link
Contributor

nrb commented Oct 30, 2025

Running the unit tests locally, I'm not able to get it to fail, so not sure what's going on with CI.

I think this is all reasonable, just need to remove a stray comment.

@tthvo
Copy link
Member Author

tthvo commented Oct 30, 2025

/verified by unit test and testwith openshift/installer#9930

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 30, 2025
@openshift-ci-robot
Copy link

@tthvo: This PR has been marked as verified by unit test and testwith https://github.com/openshift/installer/pull/9930.

Details

In response to this:

/verified by unit test and testwith openshift/installer#9930

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.

@tthvo
Copy link
Member Author

tthvo commented Oct 30, 2025

Running the unit tests locally, I'm not able to get it to fail, so not sure what's going on with CI.

Local unit test passed quite consistently for me too 👀 I guess the test is flaky? It passed now on CI: ci/prow/unit 😁

@nrb
Copy link
Contributor

nrb commented Oct 30, 2025

I guess the test is flaky?

Yeah, I wasn't able to reproduce these failures, either.

Looks like right now quay might be having issues.

@tthvo
Copy link
Member Author

tthvo commented Oct 30, 2025

/retest-required

Let's see if things are back to normal 👀

@tthvo
Copy link
Member Author

tthvo commented Oct 30, 2025

/test e2e-aws-ovn

@tthvo
Copy link
Member Author

tthvo commented Nov 3, 2025

/retest

@RadekManak
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2025
@mtulio
Copy link
Contributor

mtulio commented Nov 11, 2025

/lgtm

@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jan 21, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2026
In dual-stack environment, the CCM expects NodeIPFamilies to be in the format:

NodeIPFamilies=ipv4
NodeIPFamilies=ipv6

However, iniv1 is serializing go slices as comma-separated list, for example:

NodeIPFamilies=ipv4,ipv6

This commit ensures the original NodeIPFamilies field is kept as-is after transforming.
@tthvo
Copy link
Member Author

tthvo commented Feb 2, 2026

/verified by @tthvo (with installer PR#9930)

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 2, 2026
@openshift-ci-robot
Copy link

@tthvo: This PR has been marked as verified by @tthvo (with installer PR#9930).

Details

In response to this:

/verified by @tthvo (with installer PR#9930)

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.

@nrb
Copy link
Contributor

nrb commented Mar 2, 2026

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2026
@tthvo
Copy link
Member Author

tthvo commented Mar 2, 2026

/test vet

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

@tthvo: 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-merge-bot openshift-merge-bot bot merged commit 9816344 into openshift:main Mar 2, 2026
13 checks passed
@tthvo tthvo deleted the CORS-4209 branch March 3, 2026 00:45
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants