You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the initial dynamic config set by setup_dynamic_config is lost, TraefikProxy never checks and restores the config. It has all the information needed to do so, it just doesn't check.
This can happen e.g. when the storage backend restarts without persistence (seen in #242) or there is data loss.
Restarting the Hub works to restore everything.
How to reproduce
Launch redis-server with no persistence
launch jupyterhub with traefik_redis
restart redis-server (state lost)
attempt a launch, it won't work
Expected behaviour
dynamic config is checked periodically and recreated, just like the routing table. This should perhaps be added to check_routes
Actual behaviour
dynamic config can only be recreated by restarting the Hub
The text was updated successfully, but these errors were encountered:
Bug description
If the initial dynamic config set by
setup_dynamic_config
is lost, TraefikProxy never checks and restores the config. It has all the information needed to do so, it just doesn't check.This can happen e.g. when the storage backend restarts without persistence (seen in #242) or there is data loss.
Restarting the Hub works to restore everything.
How to reproduce
traefik_redis
Expected behaviour
dynamic config is checked periodically and recreated, just like the routing table. This should perhaps be added to
check_routes
Actual behaviour
dynamic config can only be recreated by restarting the Hub
The text was updated successfully, but these errors were encountered: