-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Bug] Upgrade from 0.22.3 to 0.23.0-beta2 loses/forgets routes #2063
Comments
Could you query in the database to see if they are present? Are they dropped or just not migrated/readable? |
The routes table is empty, advertising new route is not populating it either. |
do you have a copy of the database I could have? |
I've emailed the upgraded DB to you |
Do you also have the 0.22.3 backup? that is what I would need for testing. |
This should be fixed in #2076, some old poor design of migration is biting us and we dont have enough of an overview to cover all cases. Thanks for reporting, would be great if you can test that branch, otherwise I'll merge and do a new beta soon. |
Is this a support request?
Is there an existing issue for this?
Current Behavior
Routes that are advertised and approved in instance running version 0.22.3 are lost/forgotten after upgrading the config to 0.23.0-beta2. Also re-advertising the routes on the nodes that already shared them do not show up at all, restarting device or tailscale service doesn't seem to have any effect.
Expected Behavior
Routes migrated, show up under routes and other nodes can access them.
Steps To Reproduce
docker-compose.yml
Advertise routes, check that the show up
Change compose file
image: headscale/headscale:v0.23.0-beta2
,command: serve
Check routes, and re-advertise
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: