OCPBUGS-60525: Add NetworkPolicy as a supported kind

[anik120]

Upstream-repository: operator-registry
Upstream-commit: 919aefdce3f4d6b77c3872df249815d20749db94

[openshift-ci-robot]

@anik120: This pull request references Jira Issue OCPBUGS-60525, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-60525 to depend on a bug targeting a version in 4.20.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

Upstream-repository: operator-registry
Upstream-commit: 919aefdce3f4d6b77c3872df249815d20749db94

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.

[anik120]

/jira refresh

[openshift-ci-robot]

@anik120: This pull request references Jira Issue OCPBUGS-60525, which is invalid:

• expected dependent Jira Issue OCPBUGS-60435 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
• expected dependent Jira Issue OCPBUGS-60435 to target a version in 4.20.0, but it targets "4.20" 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.

Details

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.

[anik120]

/jira refresh

[openshift-ci-robot]

@anik120: This pull request references Jira Issue OCPBUGS-60525, which is invalid:

• expected dependent Jira Issue OCPBUGS-60435 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.

Details

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.

[anik120]

/hold

I have to update the PR to include a "allow-all" NP for the openshift-operators namespace

[anik120]

/hold cancel

note to reviewers: I add to pull in the allow-all NP manually, since this commit which has a lot of NP stuff included the openshift-operators namespace NP too.

[anik120]

verify is failing because the manual commit has Upstream: <carry> in it, since there's no upstream PR number for it.

If anyone has a better idea for what should go in the commit message I'm happy to switch it to that.

[kuiwang02]

@anik120
pre-verification failed. please refer to https://issues.redhat.com/browse/OCPBUGS-60525 for the detailed.

[anik120]

@kuiwang02 looks like I'd missed a commit earlier. It should pass now. PTAL, thank you!

[kuiwang02]

pre-verify with pass. please refer to the jira ticket's comment. thanks

[anik120]

/retest

[anik120]

/hold cancel

/jira refresh

[openshift-ci-robot]

@anik120: This pull request references Jira Issue OCPBUGS-60525, which is invalid:

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

Details

In response to this:

/hold cancel

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

[anik120]

/jira refresh

[openshift-ci-robot]

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

Requesting review from QA contact:
/cc @kuiwang02

Details

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.

[anik120]

/test e2e-gcp-olm

[grokspawn]

Looks like the verify is complaining because the manifest verification detects changes. Let me know when that's resolved, and I'll take another look.

[anik120]

Looks like the verify is complaining because the manifest verification detects changes. Let me know when that's resolved, and I'll take another look.

@grokspawn regenerated and pushed a new commit, it's passing now, PTAL

[grokspawn]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, grokspawn

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:

• DOWNSTREAM_OWNERS [grokspawn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8bcf155 and 2 for PR HEAD cd2a2af in total

[openshift-ci]

@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/okd-scos-e2e-aws-ovn	cd2a2af	link	false	/test okd-scos-e2e-aws-ovn

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-ci-robot]

@anik120: Jira Issue OCPBUGS-60525: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#1047

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

Details

In response to this:

Upstream-repository: operator-registry
Upstream-commit: 919aefdce3f4d6b77c3872df249815d20749db94

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]

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.19.0-202508190140.p0.g5c83a8a.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.19.0-202508190140.p0.g5c83a8a.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.19.0-202508190140.p0.g5c83a8a.assembly.stream.el9.
All builds following this will include this PR.

[anik120]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@anik120: new pull request created: #1048

Details

In response to this:

/cherry-pick release-4.18

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.