-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
1. Proposed title of this feature request
Argo CD CR should include error message if reconciliation fails
2. What is the nature and description of the request?
The operator includes a status field for individual components in the Argo CD CR however it does not include an error message if reconciliation fails due to bad yaml, incorrect configuration, etc.
We should include an overall status field (Running, Error, Unknown) as well as a Status message.
The current status appears as follows:
```
status:
server: Running
notificationsController: Running
host: openshift-gitops-server-openshift-gitops.apps.home.ocplab.com
applicationController: Running
applicationSetController: Running
sso: Unknown
repo: Running
phase: Available
redis: Running
```
3. Why does the customer need this? (List the business requirements here)
Without this error message the user must comb through the operator logs to try to determine why the reconciliation failed. Without the error message its often not even clear that this occurred, you can only tell when some components are stuck in an Unknown state.
Also In the case of namespace scoped Argo CD users the user may not have access to the operator log and have to get the platform team involved to debug the problem.
Finally an overall health status would facilitate health checking in situations where an external system is managing Argo CD such as ACM or another Argo CD instance.
4. List any affected packages or components.
- is related to
-
GITOPS-5871 Argo CD CR should include error message if reconciliation fails
- New