Bug 2296533:[release-4.14] api: update ocs-operator pkg version

[Nikhil-Ladha]

Update ocs-operator pkg version to include new api changes
Ref BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2276694

[openshift-ci]

@Nikhil-Ladha: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.14] api: update ocs-operator pkg version

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]

@Nikhil-Ladha: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.14] api: update ocs-operator pkg version

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.

[iamniting]

Can you move the new require block in the existing require block?

Can we reduce these other packages update?

[Nikhil-Ladha]

Can you move the new require block in the existing require block?

Can we reduce these other packages update?

I have moved the require modules to one section, but other package updates can't be controlled they come automatically due to ocs-operator upgrade as dependencies.

[iamniting]

/override ci/prow/odf-operator-e2e-aws

[openshift-ci]

@iamniting: Overrode contexts on behalf of iamniting: ci/prow/odf-operator-e2e-aws

In response to this:

/override ci/prow/odf-operator-e2e-aws

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.

[Nikhil-Ladha]

/retest

[openshift-ci]

@Nikhil-Ladha: This pull request references Bugzilla bug 2296533, 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.14.12) matches configured target release for branch (ODF 4.14.12)
• bug is in the state ASSIGNED, 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 ([email protected]), skipping review request.

In response to this:

Bug 2296533: [release-4.14] api: update ocs-operator pkg version

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.

[Nikhil-Ladha]

/retest

[Nikhil-Ladha]

/retest

[iamniting]

Is it possible to reduce these changes and only updates OCS?

[Nikhil-Ladha]

Is it possible to reduce these changes and only updates OCS?

Only ocs-operator is updated, rest of the changes are brought along by ocs-op itself.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, Nikhil-Ladha

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 [iamniting]

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

[openshift-ci]

@Nikhil-Ladha: All pull requests linked via external trackers have merged:

• red-hat-storage/odf-operator#422

Bugzilla bug 2296533 has been moved to the MODIFIED state.

In response to this:

Bug 2296533:[release-4.14] api: update ocs-operator pkg version

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.