Skip to content

Conversation

@trozet
Copy link
Contributor

@trozet trozet commented Jan 9, 2025

UDN namespace label will be required when namespaces are created in order to use a primary UDN in that namespace.

Upstream PR: ovn-kubernetes/ovn-kubernetes#4912

@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 Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

@trozet: This pull request references Jira Issue OCPBUGS-42609, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

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:

UDN namespace label will be required when namespaces are created in order to use a primary UDN in that namespace.

Upstream PR: ovn-kubernetes/ovn-kubernetes#4912

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 JacobTanenbaum and abhat January 9, 2025 16:25
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2025
@trozet
Copy link
Contributor Author

trozet commented Jan 9, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

@trozet: This pull request references Jira Issue OCPBUGS-42609, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mohit-sheth

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 9, 2025
@openshift-ci openshift-ci bot requested a review from mohit-sheth January 9, 2025 16:25
- apiGroups: [""]
apiVersions: ["v1"]
operations: ["UPDATE"]
resources: ["namespaces"] No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: missing an empty line

@@ -0,0 +1,30 @@
apiVersion: admissionregistration.k8s.io/v1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should only apply this if UDN is enabled

apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicy
metadata:
name: disable-udn-label-change
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make it more user friendly? something like:
user-defined-networks-namespace-label

@trozet trozet force-pushed the enforce_ns_udn_label branch from 97d773d to 215de3e Compare January 9, 2025 22:21
@trozet
Copy link
Contributor Author

trozet commented Jan 9, 2025

/testwith ?

UDN namespace label will be required when namespaces are created in
order to use a primary UDN in that namespace.

Co-authored-by: Patryk Diak <pdiak@redhat.com>
Signed-off-by: Tim Rozet <trozet@redhat.com>
@trozet trozet force-pushed the enforce_ns_udn_label branch from e6e69f5 to 4668f71 Compare January 9, 2025 22:53
@kyrtapz
Copy link
Contributor

kyrtapz commented Jan 10, 2025

/retest

@kyrtapz
Copy link
Contributor

kyrtapz commented Jan 10, 2025

/lgtm

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

openshift-ci bot commented Jan 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, trozet

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
Copy link
Contributor

openshift-ci bot commented Jan 10, 2025

@trozet: 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-aws-hypershift-ovn-kubevirt 4668f71 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/security 4668f71 link false /test security
ci/prow/e2e-openstack-ovn 4668f71 link false /test e2e-openstack-ovn
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 4668f71 link false /test e2e-vsphere-ovn-dualstack-primaryv6

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.

@trozet
Copy link
Contributor Author

trozet commented Jan 10, 2025

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jan 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 2a17ab8 into openshift:master Jan 10, 2025
31 of 35 checks passed
@openshift-ci-robot
Copy link
Contributor

@trozet: Jira Issue OCPBUGS-42609: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-42609 has not been moved to the MODIFIED state.

Details

In response to this:

UDN namespace label will be required when namespaces are created in order to use a primary UDN in that namespace.

Upstream PR: ovn-kubernetes/ovn-kubernetes#4912

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-network-operator
This PR has been included in build cluster-network-operator-container-v4.19.0-202501101641.p0.g2a17ab8.assembly.stream.el9.
All builds following this will include this PR.

bryan-cox added a commit to bryan-cox/hypershift that referenced this pull request Jan 10, 2025
openshift/cluster-network-operator#2612
introduced a new VAP to account for.

Signed-off-by: Bryan Cox <brcox@redhat.com>
@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-04-02-065200

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-04-02-170034

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-04-04-023411

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-04-04-170728

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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