Sync operation failed: one or more objects failed to apply, reason: ingresses.networking.k8s.io already exists

[chintaninfracloud]

Hi,

I recently updated my argocd from v2.1.1+aab9542 to v2.6.7+5bcd846. Since the upgrade i am facing one particular issue where in when i try to sync any new argocd app its syncs everything but last sync result is failed with error Sync operation failed: one or more objects failed to apply, reason: ingresses.networking.k8s.io "" already exists.
When i sync again Last sync result is updated to Sync Ok.

I am creating my argocd apps using applicationset. My apps contains svc, deployment and ingress.

I am using GKE cluster version 1.23.16-gke.1400

Also in recent change i updated argocd to be highly available
chintan.j ~ $ k get pods -n argocd
NAME READY STATUS RESTARTS AGE
argocd-application-controller-0 1/1 Running 0 28h
argocd-application-controller-1 1/1 Running 0 3d17h
argocd-application-controller-2 1/1 Running 0 3d16h
argocd-applicationset-controller-7f9896f959-ffqvw 1/1 Running 0 12h
argocd-dex-server-57784ccdfc-8zrcc 1/1 Running 0 3d17h
argocd-notifications-controller-f8c5999b7-rm96t 1/1 Running 0 3d17h
argocd-redis-5b6967fdfc-662gb 1/1 Terminated 0 28h
argocd-redis-5b6967fdfc-mvg66 1/1 Running 0 4h47m
argocd-redis-ha-haproxy-6c7fdd5dc5-8nwml 1/1 Running 0 3d20h
argocd-redis-ha-haproxy-6c7fdd5dc5-ffrdh 1/1 Terminated 0 12h
argocd-redis-ha-haproxy-6c7fdd5dc5-lz7z5 1/1 Running 0 3h30m
argocd-redis-ha-haproxy-6c7fdd5dc5-x6m5h 1/1 Running 0 3d20h
argocd-redis-ha-server-0 3/3 Running 0 11h
argocd-redis-ha-server-1 3/3 Running 0 27h
argocd-redis-ha-server-2 3/3 Running 0 3d20h
argocd-repo-server-586957864-hgtz8 1/1 Running 0 14h
argocd-repo-server-586957864-rjhpv 1/1 Running 1 (36h ago) 3d17h
argocd-server-674d74b5ff-djlsp 1/1 Running 0 3d17h
argocd-server-674d74b5ff-kcx9c 1/1 Running 0 2d12h
argocd-server-674d74b5ff-l6m5p

argocd app sync samsttp1clonerep-alerta --prune
TIMESTAMP GROUP KIND NAMESPACE NAME STATUS HEALTH HOOK MESSAGE
2023-04-26T19:20:12+05:30 apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Progressing
2023-04-26T19:20:12+05:30 networking.k8s.io Ingress qa2-cluster-samsttp1clonerep-greymatter alerta OutOfSync Missing
2023-04-26T19:20:12+05:30 ConfigMap qa2-cluster-samsttp1clonerep-greymatter alerta-conf Synced
2023-04-26T19:20:12+05:30 Service qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy
2023-04-26T19:20:14+05:30 apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy
2023-04-26T19:20:19+05:30 ConfigMap qa2-cluster-samsttp1clonerep-greymatter alerta-conf Synced configmap/alerta-conf configured
2023-04-26T19:20:19+05:30 Service qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy services "alerta" already exists
2023-04-26T19:20:19+05:30 apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy deployment.apps/alerta configured
2023-04-26T19:20:19+05:30 networking.k8s.io Ingress qa2-cluster-samsttp1clonerep-greymatter alerta OutOfSync Missing ingress.networking.k8s.io/alerta created
2023-04-26T19:20:19+05:30 ConfigMap qa2-cluster-samsttp1clonerep-greymatter alerta-conf Synced configmap/alerta-conf created
2023-04-26T19:20:19+05:30 Service qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy service/alerta created
2023-04-26T19:20:19+05:30 apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy deployment.apps/alerta created
2023-04-26T19:20:19+05:30 networking.k8s.io Ingress qa2-cluster-samsttp1clonerep-greymatter alerta OutOfSync Missing ingresses.networking.k8s.io "alerta" already exists
2023-04-26T19:20:19+05:30 networking.k8s.io Ingress qa2-cluster-samsttp1clonerep-greymatter alerta Synced Progressing ingresses.networking.k8s.io "alerta" already exists
2023-04-26T19:20:19+05:30 ConfigMap qa2-cluster-samsttp1clonerep-greymatter alerta-conf Synced configmap/alerta-conf configured
2023-04-26T19:20:19+05:30 Service qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy service/alerta configured
2023-04-26T19:20:19+05:30 apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy deployment.apps/alerta configured

Name: argocd/samsttp1clonerep-alerta
Project: qa2-cluster-samsttp1clonerep-greymatter
Server: https://kubernetes.default.svc
Namespace: qa2-cluster-samsttp1clonerep-greymatter
URL:
Repo:
Target: qa2-samsttp1clonerep
Path: platform-k8s/tick-applications/manifests/alerta
SyncWindow: Sync Allowed
Sync Policy:
Sync Status: Synced to qa2-samsttp1clonerep (e765bb0)
Health Status: Progressing

Operation: Sync
Sync Revision: e765bb06734ef4421cb7062f7a736756cdf56454
Phase: Failed
Start: 2023-04-26 19:20:11 +0530 IST
Finished: 2023-04-26 19:20:19 +0530 IST
Duration: 8s
Message: one or more objects failed to apply, reason: ingresses.networking.k8s.io "alerta" already exists

GROUP KIND NAMESPACE NAME STATUS HEALTH HOOK MESSAGE
ConfigMap qa2-cluster-samsttp1clonerep-greymatter alerta-conf Synced configmap/alerta-conf configured
Service qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy service/alerta configured
apps Deployment qa2-cluster-samsttp1clonerep-greymatter alerta Synced Healthy deployment.apps/alerta configured
networking.k8s.io Ingress qa2-cluster-samsttp1clonerep-greymatter alerta Synced Progressing ingresses.networking.k8s.io "alerta" already exists
FATA[0019] Operation has completed with phase: Failed

Argocd operation fails however all the resources are successfully created and after running sync again it is successful. Also I can see event count 2 for ingress instead of 1.

I am missing anything. Please let me know if more details are needed

[colinodell]

Argocd operation fails however all the resources are successfully created and after running sync again it is successful.

Were you ever able to figure this out? We're having the same problem, but with some Role and Role Binding objects.