Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #2429

/assign jluhrsen

kyrtapz and others added 8 commits January 30, 2025 16:46
Compare annotations directly if possible.
For network specific map entries only compare raw json
entries without parsing the map in full.

Co-authored-by: Tim Rozet <trozet@redhat.com>
Signed-off-by: Patryk Diak <pdiak@redhat.com>
Instead of always parsing all node/join subnets
parse the raw json map and only compute the results
for the affected network.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
Signed-off-by: Patryk Diak <pdiak@redhat.com>
Secondary network controllers should ingore resources
that do not belong to the current network.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
GetActiveNetworkForNamespace was being called in controllers that are
secondary UDN only. There is no reason to do this, and can cause
problems when a secondary NAD is being used by several namespaces,
networks.

Additionally, GetNetworkRole function is flawed with a note that says do
not call this function if a pod is not related to the network
controller. If a primary controller (not default) was to call
GetNetworkRole on a pod that doesn't belong to it, it would
unintentionally return the role as Secondary. This is not possible and
we should panic in this case. This will enforce the comment that
GetNetworkRole should not be called on a pod that has no network on this
controller.

Signed-off-by: Tim Rozet <trozet@redhat.com>
The code for default controller was checking if the role of the
controller on the pod was not primary. Really it should check if the
role is infrastructure-locked. That means there is a primary UDN and the
default controller should open ports.

Signed-off-by: Tim Rozet <trozet@redhat.com>
Services should not be started on a secondary UDN/NAD controller.
Multinetpol should not be started on a primary UDN controller.

Signed-off-by: Tim Rozet <trozet@redhat.com>
Order of status may not always be predictable. Allow for it.

Signed-off-by: Tim Rozet <trozet@redhat.com>
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 30, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-4930

Details

In response to this:

This is an automated cherry-pick of #2429

/assign jluhrsen

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 abhat and jcaamano January 30, 2025 16:47
@jluhrsen
Copy link
Contributor

extra tests...

/test e2e-metal-ipi-ovn-ipv6-techpreview
/test e2e-aws-ovn-hypershift-conformance-techpreview
/test e2e-azure-ovn-techpreview
/test e2e-metal-ipi-ovn-dualstack-techpreview
/test e2e-vsphere-ovn-techpreview
/test e2e-aws-ovn-techpreview
/test e2e-gcp-ovn-techpreview
/test e2e-metal-ipi-ovn-techpreview
/test openshift-e2e-gcp-ovn-techpreview-upgrade

also, let's get a look at payload jobs:

/payload 4.18 ci blocking
/payload 4.18 nightly blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

@jluhrsen: trigger 4 job(s) of type blocking for the ci release of OCP 4.18

  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fff053f0-df2c-11ef-902f-2d5b760fa4c6-0

trigger 13 job(s) of type blocking for the nightly release of OCP 4.18

  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.18-fips-payload-scan
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fff053f0-df2c-11ef-902f-2d5b760fa4c6-1

@jluhrsen
Copy link
Contributor

/retitle [release-4.18] OCPBUGS-48710: DownStream Merge Sync from 4.19 [01-29-2025]

@openshift-ci openshift-ci bot changed the title [release-4.18] SDN-4930: [DownstreamMerge] 1-29-25 [release-4.18] OCPBUGS-48710: DownStream Merge Sync from 4.19 [01-29-2025] Jan 30, 2025
@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 30, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-48710, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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:

This is an automated cherry-pick of #2429

/assign jluhrsen

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.

@jluhrsen
Copy link
Contributor

/jira refresh

@trozet
Copy link
Contributor

trozet commented Jan 30, 2025

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 30, 2025
@trozet
Copy link
Contributor

trozet commented Jan 30, 2025

/approve

@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 30, 2025
@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/override ci/prow/e2e-aws-ovn-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/e2e-aws-ovn-upgrade

Details

In response to this:

/override ci/prow/e2e-aws-ovn-upgrade

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.

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/override ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/override ci/prow/4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

Details

In response to this:

/override ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

Details

In response to this:

/override ci/prow/4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

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.

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/override ci/prow/e2e-aws-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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.

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

Azure etcd failure

/override ci/prow/e2e-azure-ovn-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/e2e-azure-ovn-upgrade

Details

In response to this:

Azure etcd failure

/override ci/prow/e2e-azure-ovn-upgrade

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.

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 31, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f3d89b2 and 2 for PR HEAD b3fc2c9 in total

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-windows

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@trozet: Overrode contexts on behalf of trozet: ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration, ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration, ci/prow/e2e-aws-ovn-windows

Details

In response to this:

/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-windows

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.

@trozet
Copy link
Contributor

trozet commented Jan 31, 2025

/tide refresh

@openshift-merge-bot openshift-merge-bot bot merged commit 9f68300 into openshift:release-4.18 Jan 31, 2025
33 of 40 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-48710: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #2429

/assign jluhrsen

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

openshift-ci bot commented Jan 31, 2025

@openshift-cherrypick-robot: 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-ovn-upgrade-local-gateway b3fc2c9 link true /test e2e-aws-ovn-upgrade-local-gateway
ci/prow/security b3fc2c9 link false /test security
ci/prow/e2e-aws-ovn-single-node-techpreview b3fc2c9 link false /test e2e-aws-ovn-single-node-techpreview
ci/prow/e2e-aws-ovn-virt-techpreview b3fc2c9 link false /test e2e-aws-ovn-virt-techpreview
ci/prow/e2e-metal-ipi-ovn-ipv6-techpreview b3fc2c9 link false /test e2e-metal-ipi-ovn-ipv6-techpreview
ci/prow/e2e-aws-ovn-upgrade b3fc2c9 link true /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-serial b3fc2c9 link true /test e2e-aws-ovn-serial
ci/prow/e2e-ovn-hybrid-step-registry b3fc2c9 link false /test e2e-ovn-hybrid-step-registry
ci/prow/okd-scos-e2e-aws-ovn b3fc2c9 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade b3fc2c9 link true /test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-techpreview b3fc2c9 link false /test e2e-vsphere-ovn-techpreview

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

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-base
This PR has been included in build ose-ovn-kubernetes-base-container-v4.18.0-202501310402.p0.g9f68300.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-microshift
This PR has been included in build ovn-kubernetes-microshift-container-v4.18.0-202501310402.p0.g9f68300.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-ovn-kubernetes
This PR has been included in build ose-ovn-kubernetes-container-v4.18.0-202501310402.p0.g9f68300.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-06-26-034047

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-10-23-005402

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-12-24-222251

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.