02:48:30.13 INFO  ==> about to run the command: timeout 90 valkey-cli -h valkey.openstack.svc.cluster.local -p 26379 --tls --cert /opt/bitnami/valkey/certs/tls.crt --key /opt/bitnami/valkey/certs/tls.key --cacert /opt/bitnami/valkey/certs/ca.crt sentinel get-primary-addr-by-name atmosphere
1:X 05 Jun 2026 02:51:40.445 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1:X 05 Jun 2026 02:51:40.445 * Valkey version=8.0.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:X 05 Jun 2026 02:51:40.445 * Configuration loaded
1:X 05 Jun 2026 02:51:40.446 * monotonic clock: POSIX clock_gettime
1:X 05 Jun 2026 02:51:40.527 * Running mode=sentinel, port=26379.
1:X 05 Jun 2026 02:51:40.533 * Sentinel ID is ec189fc48ec98a607fe05216e70822709d7fb45d
1:X 05 Jun 2026 02:51:40.533 # +monitor master atmosphere valkey-node-0.valkey-headless.openstack.svc.cluster.local 6379 quorum 2
1:X 05 Jun 2026 02:56:02.726 # +tilt #tilt mode entered
1:X 05 Jun 2026 02:56:32.796 # -tilt #tilt mode exited
1:X 05 Jun 2026 02:56:46.792 # waitpid() returned a pid (1026) we can't find in our scripts execution queue!