Pod mimir-meta-monitoring-logs-xxx with Terminating status

[hallliu1984831]

Hi There,
Please kindly help to check below issues, when I was trying to install mimir with "metaMonitoring" setting with custom value yaml and helm chart, I got bunch Terminating pods :
imir-meta-monitoring-logs-zrfbj 0/2 Terminating 0 63s node-d03
mimir-meta-monitoring-logs-zvb68 0/2 Terminating 0 18s node-d02
mimir-meta-monitoring-logs-zzgvq 0/2 Terminating 0 21s node-d03
...... More

No idea why helm install leads to above pods to Terminating status, I also tried to check logs of one pod then got below logs:
kubectl logs mimir-meta-monitoring-logs-zzgvq -n mimir-test
Error from server (BadRequest): container "grafana-agent" in pod "mimir-meta-monitoring-logs-zzgvq" is waiting to start: ContainerCreating

above pods control component:
Controlled By: DaemonSet/mimir-meta-monitoring-logs

Please kindly help to clarify what's wrong on earth, thanks

[hallliu1984831]

Per further check, I found below information for reference:
I installed both loki and mimir under same kubernetes cluster but different namespace, each installation would setup a daemonset by this CDR: https://github.com/grafana/agent/tree/main/production/operator/crds
It seems that these two daemonsets are conflict with each other, when second daemonset available then all log pods (mimir-meta-monitoring-logs-xxx, loki-logs-xxx) would become Terminating status

[hallliu1984831]

Issue fixed, the reason is have more than one Agent operator installed under two namespaces of one cluster.