Bug 2089552: [release-4.11] ocs-to-ocs: fix: rbac and GVK

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1674

/assign Madhu-1

[Madhu-1]

/assign @agarwal-mudit

[Madhu-1]

/title Bug 2083993: [release-4.11] ocs-to-ocs: fix: rbac and GVK

[Madhu-1]

/retitle Bug 2083993: [release-4.11] ocs-to-ocs: fix: rbac and GVK

[openshift-ci]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2083993, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2083993: [release-4.11] ocs-to-ocs: fix: rbac and GVK

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-cherrypick-robot: 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/red-hat-storage-ocs-ci-e2e-aws	6c1518d	link	false	/test red-hat-storage-ocs-ci-e2e-aws

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/test-infra repository. I understand the commands that are listed here.

[Madhu-1]

/retitle Bug 2089552: [release-4.11] ocs-to-ocs: fix: rbac and GVK

[openshift-ci]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2089552, which is invalid:

• expected the bug to target the "ODF 4.11.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2089552: [release-4.11] ocs-to-ocs: fix: rbac and GVK

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.

[Madhu-1]

/bugzilla refresh

[openshift-ci]

@Madhu-1: This pull request references Bugzilla bug 2089552, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (ODF 4.11.0) matches configured target release for branch (ODF 4.11.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

In response to this:

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

[agarwal-mudit]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [agarwal-mudit]

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-cherrypick-robot: All pull requests linked via external trackers have merged:

• red-hat-storage/ocs-operator#1694

Bugzilla bug 2089552 has been moved to the MODIFIED state.

In response to this:

Bug 2089552: [release-4.11] ocs-to-ocs: fix: rbac and GVK

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.