Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-08-25-155239_amd64-2025-08-25_arm64-2025-08-27#5376

Merged
openshift-merge-bot[bot] merged 7 commits intoopenshift:release-4.19from
pacevedom:rebase-2e818f160-4.19.0-0.nightly-2025-08-25-155239_amd64-2025-08-25_arm64-2025-08-27
Aug 28, 2025
Merged

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-08-25-155239_amd64-2025-08-25_arm64-2025-08-27#5376
openshift-merge-bot[bot] merged 7 commits intoopenshift:release-4.19from
pacevedom:rebase-2e818f160-4.19.0-0.nightly-2025-08-25-155239_amd64-2025-08-25_arm64-2025-08-27

Conversation

@pacevedom
Copy link
Contributor

@pacevedom pacevedom commented Aug 28, 2025

Contains manual fix for the OLM network policy yaml, which was backported from 4.20 recently.

Which issue(s) this PR addresses:

Closes #

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 28, 2025
@openshift-ci-robot
Copy link

@pacevedom: This pull request explicitly references no jira issue.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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 review from ggiguash and vanhalenar August 28, 2025 10:32
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2025
@pacevedom
Copy link
Contributor Author

/retest

@pacevedom pacevedom force-pushed the rebase-2e818f160-4.19.0-0.nightly-2025-08-25-155239_amd64-2025-08-25_arm64-2025-08-27 branch from 6bb19dc to 5b5ca2d Compare August 28, 2025 10:53
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 28, 2025

@pacevedom: all tests passed!

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.

@pacevedom
Copy link
Contributor Author

/label backport-risk-assessed
/label jira/valid-bug
/label cherry-pick-approved

@openshift-ci openshift-ci bot added 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Aug 28, 2025
@ggiguash
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Aug 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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-merge-bot openshift-merge-bot bot merged commit 1d40619 into openshift:release-4.19 Aug 28, 2025
13 checks passed
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. 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

Development

Successfully merging this pull request may close these issues.

3 participants