Skip to content

Conversation

anik120
Copy link
Contributor

@anik120 anik120 commented Aug 20, 2025

Manual cherry-pick of #1047

rashmigottipati and others added 2 commits August 20, 2025 13:52
Signed-off-by: Anik Bhattacharjee <[email protected]>
Upstream-repository: operator-registry
Upstream-commit: 919aefdce3f4d6b77c3872df249815d20749db94
Signed-off-by: Rashmi Gottipati <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: d7aaeb11ab80f862fc9c70dfb7865158bb67e28c
Copy link
Contributor

openshift-ci bot commented Aug 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2025
@perdasilva
Copy link
Contributor

/retest

@oceanc80
Copy link
Contributor

/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 Aug 25, 2025
@Xia-Zhao-rh
Copy link

/retest

@Xia-Zhao-rh
Copy link

Test PASS

/label qe-approved

xzha@xzha1-mac OCP-82135 % oc get csv
NAME                DISPLAY      VERSION   REPLACES            PHASE
nginx82135.v2.0.0   nginx82135   2.0.0     nginx82135.v1.1.0   Succeeded
xzha@xzha1-mac OCP-82135 % oc get networkpolicy -A
NAMESPACE             NAME                    POD-SELECTOR                       AGE
openshift-operators   default-allow-all       <none>                             120m
test-1                default-deny-all        <none>                             15s
test-1                nginx82135-controller   control-plane=controller-manager   15s

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 29, 2025
@perdasilva
Copy link
Contributor

/test all

@perdasilva
Copy link
Contributor

/override verify

@jianzhangbjz
Copy link
Contributor

/verified by @Xia-Zhao-rh

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 9, 2025
@openshift-ci-robot
Copy link

@jianzhangbjz: This PR has been marked as verified by @Xia-Zhao-rh.

In response to this:

/verified by @Xia-Zhao-rh

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.

Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@perdasilva: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • verify

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-gcp-console-olm
  • ci/prow/e2e-gcp-olm
  • ci/prow/e2e-gcp-olm-flaky
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-upgrade
  • ci/prow/images
  • ci/prow/periodics-images
  • ci/prow/unit-api
  • ci/prow/unit-olm
  • ci/prow/unit-psm
  • ci/prow/unit-registry
  • ci/prow/verify
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-console-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-olm-flaky
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-ovn
  • pull-ci-openshift-operator-framework-olm-main-e2e-upgrade
  • pull-ci-openshift-operator-framework-olm-main-images
  • pull-ci-openshift-operator-framework-olm-main-periodics-images
  • pull-ci-openshift-operator-framework-olm-main-unit-api
  • pull-ci-openshift-operator-framework-olm-main-unit-olm
  • pull-ci-openshift-operator-framework-olm-main-unit-psm
  • pull-ci-openshift-operator-framework-olm-main-unit-registry
  • pull-ci-openshift-operator-framework-olm-main-verify
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override verify

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.

@perdasilva
Copy link
Contributor

/override ci/prow/verify

We're ok with these staging changes

Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@perdasilva: Overrode contexts on behalf of perdasilva: ci/prow/verify

In response to this:

/override ci/prow/verify

We're ok with these staging changes

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.

@perdasilva
Copy link
Contributor

/retest

1 similar comment
@perdasilva
Copy link
Contributor

/retest

@perdasilva
Copy link
Contributor

/retest

Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@anik120: The following test 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/verify bc29458 link true /test verify

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.

@perdasilva
Copy link
Contributor

/retitle OCPBUGS-61470: [release-4.13] Add NetworkPolicy as a supported kind

@openshift-ci openshift-ci bot changed the title [release-4.13] Add NetworkPolicy as a supported kind OCPBUGS-61470: [release-4.13] Add NetworkPolicy as a supported kind Sep 9, 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 Sep 9, 2025
@openshift-ci-robot
Copy link

@anik120: This pull request references Jira Issue OCPBUGS-61470, which is invalid:

  • expected dependent Jira Issue OCPBUGS-61469 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

In response to this:

Manual cherry-pick of #1047

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.

@tmshort
Copy link
Contributor

tmshort commented Sep 10, 2025

/lgtm

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

tmshort commented Sep 10, 2025

/jira refresh

@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-61470, which is invalid:

  • expected dependent Jira Issue OCPBUGS-61469 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

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.

@perdasilva
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-61470, which is invalid:

  • expected dependent Jira Issue OCPBUGS-61469 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

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.

@perdasilva
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 10, 2025
@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-61470, 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.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-61469 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-61469 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.z
  • bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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 openshift-ci bot requested a review from Xia-Zhao-rh September 10, 2025 07:02
@openshift-merge-bot openshift-merge-bot bot merged commit 5f66f1a into openshift:release-4.13 Sep 10, 2025
13 checks passed
@openshift-ci-robot
Copy link

@anik120: Jira Issue Verification Checks: Jira Issue OCPBUGS-61470
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61470 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

Manual cherry-pick of #1047

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: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.13.0-202509100857.p0.g5f66f1a.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.13.0-202509100857.p0.g5f66f1a.assembly.stream.el8.
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
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. 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. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.