search

openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.49k stars 4.7k forks source link

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

Closed openshift-cherrypick-robot closed 2 days ago

openshift-cherrypick-robot commented 3 weeks ago

This is an automated cherry-pick of #29220

/assign tssurya

openshift-ci-robot commented 3 weeks ago

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

In response to [this](https://github.com/openshift/origin/pull/29259): >This is an automated cherry-pick of #29220 > >/assign tssurya Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
jluhrsen commented 2 weeks ago

/test e2e-aws-ovn-techpreview

openshift-ci[bot] commented 2 weeks ago

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

The following commands are available to trigger optional jobs:

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

In response to [this](https://github.com/openshift/origin/pull/29259#issuecomment-2463232347): >/test e2e-aws-ovn-techpreview > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
jluhrsen commented 2 weeks ago

/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 commented 2 weeks ago

just for my reference, this PR needs to merge first and then in order it's: https://github.com/openshift/origin/pull/29241 https://github.com/openshift/origin/pull/29244 https://github.com/openshift/origin/pull/29250

danwinship commented 6 days ago

/approve /label backport-risk-assessed

But I'm not sure I can do the label...

openshift-ci[bot] commented 6 days ago

@danwinship: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to [this](https://github.com/openshift/origin/pull/29259#issuecomment-2479852658): >/approve >/label backport-risk-assessed > >But I'm not sure I can do the label... Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
jluhrsen commented 3 days ago

/jira refresh

openshift-ci-robot commented 3 days ago

@jluhrsen: This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18" instead.

In response to [this](https://github.com/openshift/origin/pull/29259#issuecomment-2483874318): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
jluhrsen commented 3 days ago

/lgtm

openshift-ci[bot] commented 3 days ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, jluhrsen, openshift-cherrypick-robot

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[test/extended/networking/OWNERS](https://github.com/openshift/origin/blob/release-4.17/test/extended/networking/OWNERS)~~ [danwinship] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
jluhrsen commented 2 days ago

/retitle [release-4.17] OCPBUGS-43576, SDN-4930: network_segmentation: allow multiple UDN status conditions

openshift-ci-robot commented 2 days ago

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

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.

This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18" instead.

In response to [this](https://github.com/openshift/origin/pull/29259): >This is an automated cherry-pick of #29220 > >/assign tssurya Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
jluhrsen commented 2 days ago

/jira refresh

openshift-ci-robot commented 2 days ago

@jluhrsen: This pull request references Jira Issue OCPBUGS-43576, which is invalid:

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.

This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18" instead.

In response to [this](https://github.com/openshift/origin/pull/29259#issuecomment-2486441788): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
jluhrsen commented 2 days ago

/jira refresh

openshift-ci-robot commented 2 days ago

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

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.17.z) matches configured target version for branch (4.17.z) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-43577](https://issues.redhat.com//browse/OCPBUGS-43577) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-43577](https://issues.redhat.com//browse/OCPBUGS-43577) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18" instead.

In response to [this](https://github.com/openshift/origin/pull/29259#issuecomment-2486443930): > >/jira refresh > > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot] commented 2 days ago

@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 d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-azure-ovn-upgrade d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-upgrade d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-virt-techpreview d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-aws-ovn-virt-techpreview
ci/prow/e2e-aws-ovn-single-node-techpreview-serial d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca link false /test e2e-aws-ovn-single-node-techpreview-serial
ci/prow/e2e-gcp-ovn-techpreview-serial d7fb10a6ead54fb45a38b7fb2c9fefe307ee15ca 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
jluhrsen commented 2 days ago

/test e2e-aws-ovn-serial

openshift-ci-robot commented 2 days ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-43576: 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-43576 has not been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/origin/pull/29259): >This is an automated cherry-pick of #29220 > >/assign tssurya Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-bot commented 2 days ago

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202411200304.p0.g2cd8ead.assembly.stream.el9. All builds following this will include this PR.