Arthur Lyssenko
04/16/2025, 1:13 AMsignoz-clickhouse-operator
sticks around (I'm guessing that's by design)- but when I spin the release back up it proceeds to error on the `schema-migrator-sync-init`:
{"L":"info","timestamp":"2025-04-16T01:07:19.734Z","C":"signozschemamigrator/main.go:91","M":"Running migrations in sync mode","dsn":"<tcp://admin:27>ff0399-0d3a-4bd │
│ {"L":"info","timestamp":"2025-04-16T01:07:19.734Z","C":"signozschemamigrator/main.go:104","M":"Up migrations","versions":[]} │
│ {"L":"info","timestamp":"2025-04-16T01:07:19.734Z","C":"signozschemamigrator/main.go:117","M":"Down migrations","versions":[]} │
│ {"L":"info","timestamp":"2025-04-16T01:07:19.734Z","C":"signozschemamigrator/main.go:127","M":"Parsed DSN","optsError":"json: unsupported type: func(context.Contex │
│ {"L":"info","timestamp":"2025-04-16T01:07:19.734Z","C":"signozschemamigrator/main.go:133","M":"Opened connection"} │
│ Error: failed to bootstrap migrations: failed to create dbs │
│ failed to create dbs │
│ dial tcp: lookup signoz-clickhouse on 172.20.0.10:53: no such host │
│ Usage: │
│ signoz-schema-migrator sync [flags] │
│ │
│ Flags: │
│ --down string Down migrations to run, comma separated. Must provide down migrations explicitly to run │
│ -h, --help help for sync │
│ --up string Up migrations to run, comma separated. Leave empty to run all up migrations │
│ │
│ Global Flags: │
│ --cluster-name string Cluster name to use while running migrations (default "cluster") │
│ --dev Development mode │
│ --dsn string Clickhouse DSN │
│ --replication Enable replication │
│
I'm only able to make things work if I blow everything away via
kubectl delete namespace platform-monitoring
my values.yaml
isn't too exciting: https://gist.github.com/alyssenko-fliff/487d5edf1e0af086178821b1e7fd4a85 - what exactly is the issues that's preventing me from bouncing the release w/o having to completely blow things (pvcs, namespace) away?Nagesh Bansal
04/16/2025, 8:39 AMArthur Lyssenko
04/16/2025, 5:20 PM