Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #429

/assign anik120

anik120 and others added 2 commits August 14, 2025 13:18
This is a hack to backport "NetworkPolicy object kind in bundles" support from
operator-framework/operator-registry#1675
The feature was introduced in OCP 4.20 with a operator-registry bump to v1.55.0.
Ref:
1. operator-registry v1.55.0 release: https://github.com/operator-framework/operator-registry/releases/tag/v1.55.0
2. operator-registry bump in OCP 4.20: operator-framework/operator-controller#1981
Because the upstream PR is not being backported in operator-registry to older tags (with new z stream releases),
this achieves a downstream-only backport for this feature.
Adds a Netwok Policy to the end-to-end test bundles and adds a check to
the tests that the Network Policy resources are created.

Signed-off-by: Tayler Geiger <[email protected]>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60380 has been cloned as Jira Issue OCPBUGS-60521. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles

In response to this:

This is an automated cherry-pick of #429

/assign anik120

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 changed the title [release-4.18] OCPBUGS-60380: Backporting NetworkPolicy support for OLM bundles [release-4.18] OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles Aug 14, 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 Aug 14, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-60521, which is invalid:

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

This is an automated cherry-pick of #429

/assign anik120

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 anik120 and dtfranz August 14, 2025 13:20
@anik120
Copy link
Contributor

anik120 commented Aug 14, 2025

/retitle OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles Aug 14, 2025
@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 14, 2025
@tmshort
Copy link
Contributor

tmshort commented Aug 14, 2025

/retitle OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles [release-4.18]

@openshift-ci openshift-ci bot changed the title OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles OCPBUGS-60521: Backporting NetworkPolicy support for OLM bundles [release-4.18] Aug 14, 2025
@oceanc80
Copy link
Contributor

/lgtm

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

tmshort commented Aug 14, 2025

/approve

Copy link
Contributor

openshift-ci bot commented Aug 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, tmshort

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 14, 2025
Copy link
Contributor

openshift-ci bot commented Aug 14, 2025

@openshift-cherrypick-robot: all tests passed!

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.

@kuiwang02
Copy link
Contributor

pre-verification with pass. https://issues.redhat.com/browse/OCPBUGS-60521 is updated.

@anik120
Copy link
Contributor

anik120 commented Aug 15, 2025

/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 Aug 15, 2025
@openshift-ci-robot
Copy link

@anik120: This pull request references Jira Issue OCPBUGS-60521, 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.18.z) matches configured target version for branch (4.18.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-60380 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-60380 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @kuiwang02

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

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 kuiwang02 August 15, 2025 19:20
@openshift-merge-bot openshift-merge-bot bot merged commit 000dd09 into openshift:release-4.18 Aug 15, 2025
9 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60521: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-60521 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #429

/assign anik120

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

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.18.0-202508152104.p0.g000dd09.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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.