Skip to content

Conversation

@anik120
Copy link
Contributor

@anik120 anik120 commented Aug 20, 2025

Manual cherry-pick of #1047

rashmigottipati and others added 3 commits August 20, 2025 13:28
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
@openshift-ci
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

Details 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

2 similar comments
@perdasilva
Copy link
Contributor

/retest

@perdasilva
Copy link
Contributor

/retest

@anik120
Copy link
Contributor Author

anik120 commented Aug 21, 2025

/retest-required

1 similar comment
@anik120
Copy link
Contributor Author

anik120 commented Aug 21, 2025

/retest-required

@perdasilva
Copy link
Contributor

/retest

1 similar comment
@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
@perdasilva
Copy link
Contributor

/retest

@anik120
Copy link
Contributor Author

anik120 commented Aug 27, 2025

/test e2e-gcp-olm

@grokspawn
Copy link
Contributor

This is the failure case that https://issues.redhat.com/browse/OCPBUGS-57092 was written to address.
Overriding.

/override prow/e2e-gcp-olm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

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

  • prow/e2e-gcp-olm

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.

Details

In response to this:

This is the failure case that https://issues.redhat.com/browse/OCPBUGS-57092 was written to address.
Overriding.

/override prow/e2e-gcp-olm

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.

@grokspawn
Copy link
Contributor

/override ci/prow/e2e-gcp-olm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

@grokspawn: Overrode contexts on behalf of grokspawn: ci/prow/e2e-gcp-olm

Details

In response to this:

/override ci/prow/e2e-gcp-olm

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.

@grokspawn
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@Xia-Zhao-rh
Copy link
Contributor

Test PASS
/label qe-approved

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

/retest all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@perdasilva: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-gcp-console-olm
/test e2e-gcp-olm
/test e2e-gcp-ovn
/test e2e-upgrade
/test images
/test periodics-images
/test unit-api
/test unit-olm
/test unit-psm
/test unit-registry
/test verify

The following commands are available to trigger optional jobs:

/test e2e-gcp-olm-flaky

Use /test all to run all jobs.

Details

In response to this:

/retest all

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

/test all

@jianzhangbjz
Copy link
Member

/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.

Details

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.

@perdasilva
Copy link
Contributor

/retest

@perdasilva
Copy link
Contributor

/override ci/prow/e2e-gcp-olm

cc @joelanford

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@perdasilva: Overrode contexts on behalf of perdasilva: ci/prow/e2e-gcp-olm

Details

In response to this:

/override ci/prow/e2e-gcp-olm

cc @joelanford

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

/retitle OCPBUGS-61466: [release-4.15] Add NetworkPolicy as a supported kind

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

@anik120: This pull request references Jira Issue OCPBUGS-61466, 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.15.z) matches configured target version for branch (4.15.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-60847 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-60847 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

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

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

Details

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-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 9, 2025
@openshift-ci openshift-ci bot requested a review from Xia-Zhao-rh September 9, 2025 19:08
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8585581 and 2 for PR HEAD 3497076 in total

@perdasilva
Copy link
Contributor

/override ci/prow/e2e-gcp-console-olm

cc @joelanford

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@perdasilva: Overrode contexts on behalf of perdasilva: ci/prow/e2e-gcp-console-olm

Details

In response to this:

/override ci/prow/e2e-gcp-console-olm

cc @joelanford

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-merge-bot openshift-merge-bot bot merged commit 38fcbe4 into openshift:release-4.15 Sep 9, 2025
13 checks passed
@openshift-ci-robot
Copy link

@anik120: Jira Issue Verification Checks: Jira Issue OCPBUGS-61466
✔️ 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-61466 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

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-ci
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/e2e-gcp-olm 3497076 link true /test e2e-gcp-olm

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: operator-registry
This PR has been included in build operator-registry-container-v4.15.0-202509130236.p0.g38fcbe4.assembly.stream.el9.
All builds following this will include this PR.

@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.15.0-202509131935.p0.g38fcbe4.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

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.