OCPBUGS-4704: Include already compliant polices for pre-caching

[jc-rh]

Also added a kuttl test with the catalog source policy and one of the subscription policy being compliant prior to the upgrade

[openshift-ci-robot]

@jc-rh: This pull request references Jira Issue OCPBUGS-4704, 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.13.0) matches configured target version for branch (4.13.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yliu127

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

In response to this:

Also added a kuttl test with the catalog source policy and one of the subscription policy being compliant prior to the upgrade

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/test-infra repository.

[openshift-ci]

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: yliu127.

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

In response to this:

@jc-rh: This pull request references Jira Issue OCPBUGS-4704, 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.13.0) matches configured target version for branch (4.13.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yliu127

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

In response to this:

Also added a kuttl test with the catalog source policy and one of the subscription policy being compliant prior to the upgrade

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/test-infra repository.

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/test-infra repository.

[jc-rh]

/assign @fontivan

[jc-rh]

/cc @pixelsoccupied

[fontivan]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fontivan

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:

• OWNERS [fontivan]

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

[pixelsoccupied]

New change lgtm -- but GitHub still complaining about the missing the end of line. Can you check what's happening there?

[jc-rh]

New change lgtm -- but GitHub still complaining about the missing the end of line. Can you check what's happening there?

Last line wasn't empty. Good now.

[pixelsoccupied]

Just couple of more end of file line warnings to squash

[pixelsoccupied]

/lgtm

[openshift-ci-robot]

@jc-rh: All pull requests linked via external trackers have merged:

• openshift-kni/cluster-group-upgrades-operator#401

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

In response to this:

Also added a kuttl test with the catalog source policy and one of the subscription policy being compliant prior to the upgrade

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/test-infra repository.

[jc-rh]

/cherrypick release-4.12

[openshift-cherrypick-robot]

@jc-rh: new pull request created: #402

In response to this:

/cherrypick release-4.12

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/test-infra repository.