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

SDN-5579: virt, feat gates: the UDN CRD depends on the NetSeg feat gate #29407

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

Conversation

maiqueb
Copy link
Contributor

@maiqueb maiqueb commented Jan 8, 2025

As seen in [0], and [1] the UserDefinedNetwork CRD is only installed if the NetworkSegmentation feature gate is installed - hence, we need to mark the UDN based tests with the NetworkSegmentation feature gate.

[0] - https://github.com/openshift/cluster-network-operator/blob/9d96bcc4fc4653970e135a87ce380b0fb57f0587/bindata/network/ovn-kubernetes/common/001-crd.yaml#L3154
[1] - https://github.com/openshift/cluster-network-operator/blob/9d96bcc4fc4653970e135a87ce380b0fb57f0587/pkg/network/render.go#L655

@maiqueb
Copy link
Contributor Author

maiqueb commented Jan 8, 2025

/cc @JoelSpeed

@openshift-ci openshift-ci bot requested a review from JoelSpeed January 8, 2025 12:42
@maiqueb
Copy link
Contributor Author

maiqueb commented Jan 8, 2025

/test e2e-aws-ovn-virt-techpreview

@openshift-ci openshift-ci bot requested review from danwinship and trozet January 8, 2025 12:43
@maiqueb maiqueb force-pushed the persistent-ips-set-network-seg-feat-gate-on-udn-crd-tests branch from c20156d to e57743c Compare January 8, 2025 14:36
@JoelSpeed
Copy link
Contributor

/lgtm

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

knobunc commented Jan 8, 2025

/approve

@maiqueb maiqueb changed the title virt, feat gates: the UDN CRD depends on the NetSeg feat gate SDN-5579: virt, feat gates: the UDN CRD depends on the NetSeg feat gate Jan 8, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 8, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 8, 2025

@maiqueb: This pull request references SDN-5579 which is a valid jira issue.

In response to this:

As seen in [0], and [1] the UserDefinedNetwork CRD is only installed if the NetworkSegmentation feature gate is installed - hence, we need to mark the UDN based tests with the NetworkSegmentation feature gate.

[0] - https://github.com/openshift/cluster-network-operator/blob/9d96bcc4fc4653970e135a87ce380b0fb57f0587/bindata/network/ovn-kubernetes/common/001-crd.yaml#L3154
[1] - https://github.com/openshift/cluster-network-operator/blob/9d96bcc4fc4653970e135a87ce380b0fb57f0587/pkg/network/render.go#L655

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.

@knobunc
Copy link
Contributor

knobunc commented Jan 8, 2025

/approve

Copy link
Contributor

openshift-ci bot commented Jan 8, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JoelSpeed, knobunc, maiqueb
Once this PR has been reviewed and has the lgtm label, please assign stbenjam for approval. For more information see the 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

@stbenjam
Copy link
Member

stbenjam commented Jan 8, 2025

Did these run on any of the pre-submit jobs? I don’t see any techpreview in there. You should trigger them to make sure these tests pass.

@JoelSpeed
Copy link
Contributor

@stbenjam They already run in periodic tests, see https://sippy.dptools.openshift.org/sippy-ng/tests/4.19/details?filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22contains%22%2C%22value%22%3A%22%5BOCPFeatureGate%3APersistentIPsForVirtualization%5D%22%7D%5D%7D where you can see them all already.

This is just changing the name to include an additional feature gate, it shouldn't affect the actual tests themselves other than skipping them when the new gate is not enabled

Copy link
Contributor

openshift-ci bot commented Jan 8, 2025

@maiqueb: 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-openstack-ovn e57743c link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial e57743c link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout e57743c link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade e57743c link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6 e57743c link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-upgrade e57743c link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-fips e57743c link true /test e2e-aws-ovn-fips
ci/prow/e2e-metal-ipi-ovn e57743c link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node e57743c link false /test e2e-aws-ovn-single-node
ci/prow/okd-scos-e2e-aws-ovn e57743c link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout e57743c link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd e57743c link false /test e2e-agnostic-ovn-cmd

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-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
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants