Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
1.9.0
-
None
-
False
-
None
-
False
Description
Description of problem:
Severity: Sev 2
What is the impact of your issue: Facing issue on all clusters, OCP 4.13; RedHat OpenShift Gitops Operator 1.9.0; on VMWare vSphere
Do you have a workaround in place already: NO
Customer case #: 03609958
Revenue Impact: NA
OCP Version: 4.13
Customer name: direct services Gütersloh
GitOps Operator Version: 1.9.0
Slack thread: https://redhat-internal.slack.com/archives/C05GQDTR02X/p1694627511435329 **
*
Issue:*
IHAC who is facing an issue while trying to enable syncPolicy.automated.selfHeal: true from both yaml and UI. On UI if enable it gets disable automatically. Customer is using total 6 ArgoCD on different clusters and facing same issue on every cluster. Also, they said it's been happening for many days even on older versions but as they were not using it earlier they ignored it, but now they want to use it.
I found a similar issue [https://github.com/argoproj/argo-cd/issues/3895] but it's reverse here as they are not able to disable it.
I was unable to reproduce this issue. Currently customer is using GitOps 1.9.0. In the ApplicationSet yaml we can see in annotation that syncPolicy.automated.selfHeal: true was added but it got removed. Also, they are facing issue with one more field: spec.generators.git.files.exclude; this is getting removed from the yaml but the output they are getting is correct. On the doc [https://argocd-applicationset.readthedocs.io/en/stable/Generators-Git/] files does not have exclude but directories have it and when I asked to change it excluded everything and they had to revert the changes:
~~~
Current config:
spec:
generators:
- git:
files:
- path: .bpgit-deploy/**/config.yaml
- path: .bpgit-deploy/builder
Suggested changes:
spec: generators: - git: files: - path: .bpgit-deploy/**/config.yaml directories: - path: .bpgit-deploy/builder exclude: true
With both issues above, the app stays in OutOfSync
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):