Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initial dynamic config not checked/restored if lost #247

Open
minrk opened this issue May 29, 2024 · 0 comments
Open

initial dynamic config not checked/restored if lost #247

minrk opened this issue May 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@minrk
Copy link
Member

minrk commented May 29, 2024

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

  1. Launch redis-server with no persistence
  2. launch jupyterhub with traefik_redis
  3. restart redis-server (state lost)
  4. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant