Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

network: fix generation of VIPs for single- and dual-stack setups #1628

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mkowalski
Copy link
Member

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2024
Copy link

openshift-ci bot commented Jan 23, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

openshift-ci bot commented Jan 23, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

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

@mkowalski mkowalski marked this pull request as ready for review January 23, 2024 14:36
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2024
@mkowalski
Copy link
Member Author

/cc @cybertron

@openshift-ci openshift-ci bot requested a review from cybertron January 23, 2024 14:36
@cybertron
Copy link
Contributor

/lgtm

Seems fine. I assume this is related to deploying single stack clusters on dual stack envs?

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2024
@mkowalski
Copy link
Member Author

/hold
Until manual testing proves that all works

Yes, the issue with current state is that we do not generate a valid install-config yaml for a single-stack cluster with dual-stack hosts. For such a scenario (allowed by syntax of config.sh) we put dual-stack VIPs in install-config.yaml but only single cluster network. This is illegal and does not pass the basic validations.

With this fix I want to be explicit as the VIP configuration goes. I am still not allowing to have single VIP setup with dual-stack cluster but extending feature set is not my goal, all I want first is to remove a scenario that prevents installation when in general it should work

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 23, 2024
Copy link

openshift-ci bot commented Jan 23, 2024

@mkowalski: 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
ci/prow/e2e-metal-ipi-ovn-dualstack 08803c9 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 08803c9 link false /test e2e-metal-ipi-serial-ovn-ipv6

Full PR test history. Your PR dashboard.

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/test-infra 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
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants