Skip to content

Conversation

openshift-bot
Copy link
Contributor

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2025-09-09 15:58:27 operator-framework/operator-lifecycle-manager@55a4f26 oceanc80 Test NetworkPolicy support in e2es (#3630)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

* Add NetworkPolicy to e2e tests

* Update e2e to test NP support

* Add single-bundle-index build script

Adds to script for building the single-bundle-index image used in the e2e tests. Also
adds the necessary manifests and Containerfile for the bundle in that
index, and adds a note in DEVELOPMENT.md about using the script for
updating the images used in e2e tests.

Signed-off-by: Tayler Geiger <[email protected]>

---------

Signed-off-by: Tayler Geiger <[email protected]>
Co-authored-by: Tayler Geiger <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 55a4f2635a566e02d3f40db5e69396560dbe2aae
@openshift-bot openshift-bot added 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 10, 2025
@openshift-ci-robot
Copy link

@openshift-bot: This pull request explicitly references no jira issue.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2025-09-09 15:58:27 operator-framework/operator-lifecycle-manager@55a4f26 oceanc80 Test NetworkPolicy support in e2es (#3630)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 10, 2025
Copy link
Contributor

openshift-ci bot commented Sep 10, 2025

@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-framework.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date Commit Author Message
2025-09-09 15:58:27 operator-framework/operator-lifecycle-manager@55a4f26 oceanc80 Test NetworkPolicy support in e2es (#3630)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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.

Copy link
Contributor

openshift-ci bot commented Sep 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

1 similar comment
Copy link
Contributor

openshift-ci bot commented Sep 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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

@jianzhangbjz
Copy link
Contributor

/verified by pass

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

@jianzhangbjz: This PR has been marked as verified by pass.

In response to this:

/verified by pass

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
Copy link

/retest-required

Remaining retests: 0 against base HEAD 0366121 and 2 for PR HEAD a2ef251 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 0366121 and 2 for PR HEAD a2ef251 in total

@tmshort
Copy link
Contributor

tmshort commented Sep 10, 2025

/test e2e-gcp-olm

Copy link
Contributor

openshift-ci bot commented Sep 10, 2025

@openshift-bot: 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/okd-scos-e2e-aws-ovn a2ef251 link false /test okd-scos-e2e-aws-ovn

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.

@openshift-merge-bot openshift-merge-bot bot merged commit bf3670a into openshift:main Sep 10, 2025
15 of 16 checks passed
@grokspawn
Copy link
Contributor

grokspawn commented Sep 11, 2025

/retitle OPRUN-4127: Synchronize From Upstream Repositories

@openshift-ci openshift-ci bot changed the title NO-ISSUE: Synchronize From Upstream Repositories OPRUN-4127: Synchronize From Upstream Repositories Sep 11, 2025
@grokspawn
Copy link
Contributor

grokspawn commented Sep 11, 2025

/retitle OPRUN-3966: Synchronize From Upstream Repositories

@openshift-ci openshift-ci bot changed the title OPRUN-4127: Synchronize From Upstream Repositories OPRUN-3966: Synchronize From Upstream Repositories Sep 11, 2025
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. 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. verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants