williamdclt
08/08/2022, 12:27 PMgrpc_health_probe
is returning NOT_SERVING
(screenshot 1)
- On SpiceDB side, I'm seeing this log: {"level":"debug","datastoreReady":false,"dispatchReady":true,"time":"2022-08-08T12:20:53Z","message":"completed dispatcher and datastore readiness checks"}
. That's with LOG_LEVEL=trace.
My old service on v1.7.1
has no problem: pods report healthy and can connect to the DB. Spinning up a new pod on v.1.7.1
works as well.
I can't see anything wrong database-side.
How can we know why does SpiceDB think that the datastore isn't ready?v1.11.0
pod with psql "$DBURL"
(DBURL is what's passed as --datastore-conn-uri
)v1.10.0
, so it must be a commit in this releaseecordell
08/08/2022, 1:12 PMready=false
if the migration level it's talking to doesn't equal the latest migration - when you upgraded, did you run spicedb migrate
?williamdclt
08/08/2022, 1:18 PMpre-upgrade
hook?ecordell
08/08/2022, 1:20 PMspicedb migrate head
from the version you're updating to before rolling out the new versionwilliamdclt
08/08/2022, 1:20 PMecordell
08/08/2022, 1:21 PMJoey
08/08/2022, 1:24 PM