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] OCPBUGS-41817: Update the NotFound case for CNI plugin to reflect changes #29091

Merged
merged 1 commit into from
Sep 13, 2024
Merged

[release-4.17] OCPBUGS-41817: Update the NotFound case for CNI plugin to reflect changes #29091

merged 1 commit into from
Sep 13, 2024

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #29083

/assign deads2k

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 11, 2024
Merged
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-41270 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.17] OCPBUGS-41817: Update the NotFound case for CNI plugin to reflect changes

In response to this:

This is an automated cherry-pick of #29083

/assign deads2k

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 changed the title [release-4.17] OCPBUGS-41270: Update the NotFound case for CNI plugin to reflect changes [release-4.17] OCPBUGS-41817: Update the NotFound case for CNI plugin to reflect changes Sep 11, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 11, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-41817, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.0) matches configured target version for branch (4.17.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-41270 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-41270 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #29083

/assign deads2k

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 added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 11, 2024
@openshift-ci-robot openshift-ci-robot mentioned this pull request Sep 11, 2024
Merged
@deads2k
Copy link
Contributor

deads2k commented Sep 12, 2024

/lgtm
/approve

@deads2k deads2k added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 12, 2024
@deads2k deads2k added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. labels Sep 12, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, 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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e3d16c5 and 2 for PR HEAD 706f7cb in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 12, 2024 •
edited
Loading

@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 706f7cb link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node 706f7cb link false /test e2e-aws-ovn-single-node
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 706f7cb link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-upgrade 706f7cb link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial 706f7cb link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-upgrade 706f7cb link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-azure-ovn-upgrade 706f7cb link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 706f7cb link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-rt-upgrade 706f7cb link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-ipsec-serial 706f7cb link false /test e2e-aws-ovn-ipsec-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.

@abhat
Copy link
Contributor

abhat commented Sep 12, 2024

/tide refresh

@abhat
Copy link
Contributor

abhat commented Sep 12, 2024

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit ec6389f into openshift:release-4.17 Sep 13, 2024
19 of 29 checks passed
@openshift-ci-robot
Copy link

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

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

In response to this:

This is an automated cherry-pick of #29083

/assign deads2k

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: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202409130707.p0.gec6389f.assembly.stream.el9.
All builds following this will include this PR.

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

@anuragthehatter anuragthehatter Awaiting requested review from anuragthehatter

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

@sjenning sjenning Awaiting requested review from sjenning

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@sayan-biswas sayan-biswas

@kasturinarra kasturinarra

@deads2k deads2k

@jadhaj jadhaj

@pamoedom pamoedom

@jitendar-singh jitendar-singh

@prietyc123 prietyc123

@gangwgr gangwgr

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.