Bug 2262070

Description of problem (please be detailed as possible and provide log
snippests):
Network fencing is not applied on a node which is down when 'node.kubernetes.io/out-of-service=nodeshutdown:NoExecute' label is applied 

Version of all relevant components (if applicable):
OCP 4.15 and ODF 4.15.0-126

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
NA

Is there any workaround available to the best of your knowledge?
NA

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
NA

Steps to Reproduce:
1. Install Openshift data foundation and deploy a app pod in same node as that of rook ceph operator pod
2. Shutdown the node on which CephFS RWO pod is deployed
3.Once the node is down, add taint
```oc  taint nodes <node-name> node.kubernetes.io/out-of-service=nodeshutdown:NoExecute ```
Wait for some time(if the application pod and rook operator are on the same node wait for bit logger) then check the networkFence cr status 

Actual results:
Network fence is not created if the node is down, But pod gets rescheduled on the new node immedietely

Expected results:
Network fence should be created when the node is down

Additional info:
When the node is up and working if you apply the taint 'oc adm taint nodes compute-1 node.kubernetes.io/out-of-service=nodeshutdown:NoExecute' Network fence would be created