-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
3
-
False
-
-
False
-
-
-
Important
-
Customer Escalated, Customer Facing, Customer Reported
Description of problem:
$ omc get events --sort-by '{.metadata.creationTimestamp}' | grep Created
1h17m Normal SuccessfulCreate daemonset/node-agent (combined from similar events): Created pod: node-agent-dgtcc
3h Normal Created pod/node-agent-94jl4 Created container: node-agent
3h Normal Created pod/node-agent-hrksq Created container: node-agent
3h Normal Created pod/node-agent-xrl46 Created container: node-agent
3h Normal Created pod/node-agent-qs8f2 Created container: node-agent
2h56m Normal Created pod/node-agent-k8pqn Created container: node-agent
2h56m Normal Created pod/node-agent-lx8hh Created container: node-agent
2h56m Normal Created pod/node-agent-kjlct Created container: node-agent
...
3m9s Normal Created pod/node-agent-cn7gj Created container: node-agent
3m8s Normal Created pod/node-agent-f4ghx Created container: node-agent
3m7s Normal Created pod/node-agent-glxvx Created container: node-agent
Version-Release number of selected component (if applicable):
OADP 1.5.2 Openshift Container Platform 4.19.12
How reproducible:
Not tested in lab
Steps to Reproduce:
1.
2.
3.
Actual results:
node-agent is continually deployed blocking any backup from being correctly done
Expected results:
No redeployment at all as no change is being done
Additional info:
Looking for the root cause of the redeployment, it seems like adp-controller-manager pod is triggering the redeployment and looking at the API calls i see the "cloud-credentials" secrets being patched at the same pace. The "cloud-credentials" secret is manage by the "external-secrets-operator" so i suspect that maybe the combination is triggering some king of redeployment loop.
