Closed jackyalbo closed 2 months ago
Hi @jackyalbo. Thanks for your PR.
I'm waiting for a red-hat-storage member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/retest-required
@jackyalbo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/ok-to-test
/retest
@jackyalbo is this a direct revert of this https://github.com/red-hat-storage/ocs-operator/pull/2461?
@jackyalbo is this a direct revert of this #2461? No. I still want Affinity to be set in standalone but only if it is set in storageCluster spec( the ok check). I'm trying not to hurt the flow for non-standalone - which failed the unit test.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jackyalbo, malayparida2000, umangachapagain
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
/cherry-pick release-4.17
@malayparida2000: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.
@malayparida2000: new pull request created: #2801
Fix for https://bugzilla.redhat.com/show_bug.cgi?id=2311551
We revert the nodeAffinity change to apply only to cases where users explicitly set nodeAffinity in storage cluster spec.