-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
1.8.0
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 255, GITOPS Service EE Sprint 256, GITOPS Service EE Sprint 257, GITOPS Service EE Sprint 258
Description of problem:
The Operator constantly updates the .status field of the ArgoCD CR even when the status doesn't change, or the state is flapping unexpectedly.
This leads to unnecessary updates of the resource, and in turn will prevent updating the resource using the DevConsole UI's YAML editor.
Prerequisites (if any, like setup, operators/versions):
Tested with a vanilla installation of GitOps 1.7.2
Steps to Reproduce
- Create new ArgoCD CR somewhere
- Set something in the CR so that something doesn't work as expected (in my example, I just set .spec.ha.enabled to true which leads to some error state without further configuration)
Actual results:
- States are flapping between Pending and Available
- This leads to constant updates of the resource
- This leads to the situation where you can't fix the error using the DevConsole UI (e.g. to turn .spec.ha.enabled back to false)
Expected results:
- Status only updated once, without flapping
- Single resource update
- Being able to fix the error using the DevConsole UI
ACCEPTANCE CRITERIA
- Add a unit test
- Make sure the status is not continuously reconciled
- Bad user experience from DevConsole API is fixed (DevConsole show the message - Object has been updated ....)
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Additional info (Such as Logs, Screenshots, etc):
See attached screen recording