This message was deleted.
# supports
Slackbot
02/26/2024, 11:02 PMThis message was deleted.
✅ 1
n
Nicolas Rakover
02/26/2024, 11:02 PM Copy code
kubectl -n signoz get pods
NAME READY STATUS RESTARTS AGE
signoz-release-1-alertmanager-0 0/1 Init:0/1 0 168m
signoz-release-1-clickhouse-operator-68f766878c-xfx8c 2/2 Running 0 5m28s
signoz-release-1-frontend-c6cb6b5c9-mrwdj 0/1 Init:0/1 0 168m
signoz-release-1-otel-collector-745d5c84c8-79b4p 0/1 Init:0/1 0 168m
signoz-release-1-otel-collector-metrics-6cdcf5b7cc-n7wqh 0/1 Init:0/1 0 168m
signoz-release-1-query-service-0 0/1 Init:0/1 0 168m
signoz-release-1-schema-migrator-init-c4n4g 0/1 Init:0/2 0 8m16s
signoz-release-1-zookeeper-0 1/1 Running 0 12mn
nitya-signoz
02/27/2024, 3:01 AM@Prashant Shahi ^
🙏 1
p
Prashant Shahi
02/27/2024, 3:03 AMThis behaviour is seen when previously installed clickhouse is not cleaned up properly.
Can you follow through the cleanup instructions below and retry the installation?
https://signoz.io/docs/operate/kubernetes/#uninstall-signoz-cluster
n
Nicolas Rakover
02/27/2024, 3:17 AM@Prashant Shahi I'd rather not blow away all of our data and config -- if this is the only path at this point I'll do it, but to be clear the troubles started when doing a perfectly vanilla
helm upgrade0.38.2Nicolas Rakover
02/27/2024, 3:20 AMI didn't know about the Clickhouse
finalizersNicolas Rakover
02/27/2024, 3:23 AMHmm I actually don't have any
clickhouseinstallationp
Prashant Shahi
02/27/2024, 3:48 AMunclean uninstall is known is cause this issue of CHI or CHI pods disappearance.
Prashant Shahi
02/27/2024, 3:49 AMYou could
helm upgradePrashant Shahi
02/27/2024, 3:49 AMAll others pods would be stuck in Init waiting for CHI pods.
n
Nicolas Rakover
02/27/2024, 6:07 PMDoing a
helm upgrade🙌 1
2 Views