Bug 2314636: [release-4.17] Clear the affinity on Noobaa if it was set previously to handle upgrades #2852
Conversation
We are adding affinity to Noobaa if not in noobaa-standalone mode or if placement is specified. But we are not clearing the affinity if the affinity was set previously. This is breaking upgrade. Signed-off-by: Malay Kumar Parida <[email protected]>
malayparida2000
changed the title
openshift-ci
bot
added
the
bugzilla/severity-high
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2314636, 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
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:
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
bot
added
the
bugzilla/valid-bug
|
/lgtm |
|
[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:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
openshift-merge-bot
bot
merged commit 83e4ff1
into
red-hat-storage:release-4.17
|
@openshift-cherrypick-robot: An error was encountered searching for external tracker bugs for bug 2314636 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
could not parse external identifier "noobaa/noobaa-operator/pull/1453/commits" as pull: invalid pull identifier with 5 parts: "noobaa/noobaa-operator/pull/1453/commits"
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
This is an automated cherry-pick of #2851
/assign malayparida2000