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.

Sign up for GitHub

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

Jump to bottom

[release-4.17] SDN-4930: network_segmentation: allow multiple UDN status conditions #29259

Open
wants to merge 1 commit into
base: release-4.17
Choose a base branch
from
Open

[release-4.17] SDN-4930: network_segmentation: allow multiple UDN status conditions #29259

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #29220

/assign tssurya

@npinaeva
network_segmentation: allow multiple UDN status conditions.
d7fb10a 
Fix UDN status check to assert required condition is
present in the status instead of checking that status
has only 1 condition.

Signed-off-by: Nadia Pinaeva <[email protected]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Nov 1, 2024
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 1, 2024 •
edited by openshift-ci bot
Loading

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

In response to this:

This is an automated cherry-pick of #29220

/assign tssurya

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.

@tssurya tssurya mentioned this pull request Nov 1, 2024
Closed
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Nov 1, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign trozet 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

@jluhrsen
Copy link
Contributor

jluhrsen commented Nov 7, 2024

/test e2e-aws-ovn-techpreview

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Nov 7, 2024

@jluhrsen: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-edge-zones
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-image-registry
  • /test e2e-aws-ovn-serial
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-builds
  • /test e2e-gcp-ovn-image-ecosystem
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-metal-ipi-ovn-ipv6
  • /test images
  • /test lint
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-etcd-certrotation
  • /test e2e-aws-etcd-recovery
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-etcd-scaling
  • /test e2e-aws-ovn-ipsec-serial
  • /test e2e-aws-ovn-kube-apiserver-rollout
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-single-node-serial
  • /test e2e-aws-ovn-single-node-techpreview
  • /test e2e-aws-ovn-single-node-techpreview-serial
  • /test e2e-aws-ovn-single-node-upgrade
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upi
  • /test e2e-aws-ovn-virt-techpreview
  • /test e2e-aws-proxy
  • /test e2e-azure
  • /test e2e-azure-ovn-etcd-scaling
  • /test e2e-azure-ovn-upgrade
  • /test e2e-baremetalds-kubevirt
  • /test e2e-external-aws
  • /test e2e-external-aws-ccm
  • /test e2e-gcp-csi
  • /test e2e-gcp-disruptive
  • /test e2e-gcp-fips-serial
  • /test e2e-gcp-ovn-etcd-scaling
  • /test e2e-gcp-ovn-rt-upgrade
  • /test e2e-gcp-ovn-techpreview
  • /test e2e-gcp-ovn-techpreview-serial
  • /test e2e-metal-ipi-ovn
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-dualstack-local-gateway
  • /test e2e-metal-ipi-ovn-kube-apiserver-rollout
  • /test e2e-metal-ipi-serial
  • /test e2e-metal-ipi-serial-ovn-ipv6
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-openstack-ovn
  • /test e2e-openstack-serial
  • /test e2e-vsphere
  • /test e2e-vsphere-ovn-dualstack-primaryv6
  • /test e2e-vsphere-ovn-etcd-scaling
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-origin-release-4.17-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-origin-release-4.17-e2e-aws-csi
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-edge-zones
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-kube-apiserver-rollout
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-serial
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-release-4.17-e2e-azure-ovn-upgrade
  • pull-ci-openshift-origin-release-4.17-e2e-gcp-csi
  • pull-ci-openshift-origin-release-4.17-e2e-gcp-ovn
  • pull-ci-openshift-origin-release-4.17-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-release-4.17-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn
  • pull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-dualstack-local-gateway
  • pull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-kube-apiserver-rollout
  • pull-ci-openshift-origin-release-4.17-e2e-openstack-ovn
  • pull-ci-openshift-origin-release-4.17-e2e-vsphere-ovn-dualstack-primaryv6
  • pull-ci-openshift-origin-release-4.17-images
  • pull-ci-openshift-origin-release-4.17-lint
  • pull-ci-openshift-origin-release-4.17-unit
  • pull-ci-openshift-origin-release-4.17-verify
  • pull-ci-openshift-origin-release-4.17-verify-deps

In response to this:

/test e2e-aws-ovn-techpreview

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.

@jluhrsen
Copy link
Contributor

jluhrsen commented Nov 7, 2024

/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-virt-techpreview
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial

@jluhrsen
Copy link
Contributor

jluhrsen commented Nov 7, 2024

just for my reference, this PR needs to merge first and then in order it's:
#29241
#29244
#29250

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Nov 8, 2024

@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-metal-ipi-ovn-dualstack-local-gateway d7fb10a link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-azure-ovn-upgrade d7fb10a link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 d7fb10a link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-upgrade d7fb10a link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-virt-techpreview d7fb10a link false /test e2e-aws-ovn-virt-techpreview
ci/prow/e2e-aws-ovn-single-node-techpreview-serial d7fb10a link false /test e2e-aws-ovn-single-node-techpreview-serial
ci/prow/e2e-gcp-ovn-techpreview-serial d7fb10a link false /test e2e-gcp-ovn-techpreview-serial

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.

@jluhrsen jluhrsen mentioned this pull request Nov 13, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@danwinship danwinship Awaiting requested review from danwinship

@knobunc knobunc Awaiting requested review from knobunc

Assignees

@tssurya tssurya

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@openshift-cherrypick-robot @openshift-ci-robot @jluhrsen @tssurya @npinaeva