Skip to content

OCPBUGS-69844: Revert NetworkPolicies for LSO (OLM-managed) #568

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
Merged
openshift-merge-bot merged 1 commit into from
Dec 18, 2025
Merged

OCPBUGS-69844: Revert NetworkPolicies for LSO (OLM-managed) #568

openshift-merge-bot merged 1 commit into from
Dec 18, 2025

Conversation

@dobsonj
Copy link
Member

@dobsonj dobsonj commented Dec 18, 2025 •
edited
Loading

https://issues.redhat.com/browse/OCPBUGS-69844

This reverts #555 because our build pipeline will block release of OLM-managed operators with NetworkPolicy manifests until after the 4.21 release, see bug for details.

Reverted cleanly with:

git revert -m 1 397dcaa02032f52916aa3ed49e5b9ecd1b96cc01

/cc @openshift/storage @duanwei33

@dobsonj
OCPBUGS-69844: Revert "Merge pull request openshift#555 from dobsonj/…
d8f2486 
…STOR-2550"

This reverts commit 397dcaa, reversing
changes made to da0a470.
@openshift-ci openshift-ci bot requested a review from duanwei33 December 18, 2025 16:38
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Dec 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2025

@dobsonj: GitHub didn't allow me to request PR reviews from the following users: openshift/storage.

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

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-69844

This reverts #555 because our build pipeline will block release of OLM-managed operators until after the 4.21 release, see bug for details.

Reverted cleanly with:

git revert -m 1 397dcaa02032f52916aa3ed49e5b9ecd1b96cc01

/cc @openshift/storage @duanwei33

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-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 18, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@dobsonj: This pull request references Jira Issue OCPBUGS-69844, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

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

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-69844

This reverts #555 because our build pipeline will block release of OLM-managed operators until after the 4.21 release, see bug for details.

Reverted cleanly with:

git revert -m 1 397dcaa02032f52916aa3ed49e5b9ecd1b96cc01

/cc @openshift/storage @duanwei33

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2025
@dobsonj
Copy link
Member Author

dobsonj commented Dec 18, 2025

/cherry-pick release-4.21

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Dec 18, 2025

@dobsonj: once the present PR merges, I will cherry-pick it on top of release-4.21 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.21

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-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@dobsonj: This pull request references Jira Issue OCPBUGS-69844, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-69844

This reverts #555 because our build pipeline will block release of OLM-managed operators with NetworkPolicy manifests until after the 4.21 release, see bug for details.

Reverted cleanly with:

git revert -m 1 397dcaa02032f52916aa3ed49e5b9ecd1b96cc01

/cc @openshift/storage @duanwei33

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 Dec 18, 2025

@dobsonj: 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.

@dobsonj
Copy link
Member Author

dobsonj commented Dec 18, 2025

/verified by CI

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

openshift-ci-robot commented Dec 18, 2025

@dobsonj: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@gnufied
Copy link
Member

gnufied commented Dec 18, 2025

/lgtm
/approve

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

openshift-ci bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, gnufied

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 ea7322e into openshift:main Dec 18, 2025
8 checks passed
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@dobsonj: Jira Issue OCPBUGS-69844: All pull requests linked via external trackers have merged:

All linked pull requests have the verified tag. Jira Issue OCPBUGS-69844 has been moved to the VERIFIED state.

Details

In response to this:

https://issues.redhat.com/browse/OCPBUGS-69844

This reverts #555 because our build pipeline will block release of OLM-managed operators with NetworkPolicy manifests until after the 4.21 release, see bug for details.

Reverted cleanly with:

git revert -m 1 397dcaa02032f52916aa3ed49e5b9ecd1b96cc01

/cc @openshift/storage @duanwei33

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

openshift-cherrypick-robot commented Dec 18, 2025

@dobsonj: new pull request created: #569

Details

In response to this:

/cherry-pick release-4.21

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Dec 18, 2025
Merged
@duanwei33 duanwei33 mentioned this pull request Dec 19, 2025
Closed
@duanwei33 duanwei33 mentioned this pull request Jan 13, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@duanwei33 duanwei33 Awaiting requested review from duanwei33

Assignees

@gnufied gnufied

@chao007 chao007

@duanwei33 duanwei33

@Phaow Phaow

@radeore radeore

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@dobsonj @openshift-ci-robot @openshift-cherrypick-robot @gnufied @chao007 @duanwei33 @Phaow @radeore