Bug 2131169

Summary:	[Backport to 4.10][GSS][Nooba] Fix Tolerations setting for NooBaa in standalone mode
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Bipin Kunal <bkunal>
Component:	ocs-operator	Assignee:	Utkarsh Srivastava <usrivast>
Status:	CLOSED ERRATA	QA Contact:	Shrivaibavi Raghaventhiran <sraghave>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	belimele, etamir, kjosy, kramdoss, madam, muagarwa, nbecker, ocs-bugs, odf-bz-bot, rcyriac, sostapov, usrivast
Target Milestone:	---	Flags:	sheggodu: needinfo? (usrivast)
Target Release:	ODF 4.10.9
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2131168	Environment:
Last Closed:	2022-12-12 20:06:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2131168
Bug Blocks:

Comment 3 Sunil Kumar Acharya 2022-10-19 06:05:34 UTC

Please backport and merge the fix to ODF-4.10 stream and update the RDT flag/text appropriately.

Comment 15 Shrivaibavi Raghaventhiran 2022-12-07 18:22:14 UTC

Tested versions:
-----------------
ODF - quay.io/rhceph-dev/ocs-registry:4.10.9-7
OCP - 4.10.0-0.nightly-2022-12-06-230458

Teststeps:
1. Deploy MCG standalone
2. Taint the nodes
oc adm taint nodes compute-0 compute-1 compute-2 xyz=true:NoSchedule
3. Apply tolerations in storage CR and 4 subscriptions 
4. Observe if pods are respining automatically and coming to running state 
5. For the pods which come to running state check the pods yaml to ensure it has tolerations
6. Respin all the pods to just check if the toleration exists

Observation:
-------------
1. Noobaa-default-backing-store pods not getting automatically respinned after updating the storage cluster and subs with the required toleration.

However force restart of pod works fine. AFter force restart noobaa-default-backing store pod comes up with the desired toleration

We already have a BZ for the above observation : https://bugzilla.redhat.com/show_bug.cgi?id=2149872

** Content added to storagecluster
spec:
  placement:
    noobaa-standalone:    
      tolerations:
      - effect: NoSchedule
        key: xyz
        operator: Equal
        value: "true"
      - effect: NoSchedule
        key: node.ocs.openshift.io/storage
        operator: Equal
        value: "true"

*** Content added to all 4 subs
  config:
    tolerations:
    - effect: NoSchedule
      key: xyz
      operator: Equal
      value: "true"


Moving the BZ to verified state

Comment 19 errata-xmlrpc 2022-12-12 20:06:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Data Foundation 4.10.9 Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8934