-
Notifications
You must be signed in to change notification settings - Fork 397
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] Database srror after upgrade from 1.5.10 to 1.5.11 #1725
Comments
Hi @thelittlefireman, thank you for opening this issue. |
nothing special in my config, it's the same for a very long time. I will copy past it later. Something strang happen, the previous version is identify as i try to delete and recreate the containers with the same DB but still got the same error.
|
@thelittlefireman try changing the version in the database metadata and restart all containers: UPDATE bw_metadata SET version = 'old'; |
i try but same issue. I also try to upgrade to 1.5.12 but same errors |
View of the database
Seems to be older than 1.5.10 |
Fix by |
I had the same issue as you and tried your fix but I ended up throwing the towel and nuked the DB to let it re-create to a proper state. It's a radical fix but it worked. |
I also have the same issue but not with the scheduler container but with the ui-container. I hope someone can find a solution to the problem, as several of my instances are now affected. |
FYI guys we changed this behavior in the 1.6.X release, I'll run some tests and let you know of an easy solution about it. |
What happened?
After upgrade from 1.5.10 to 1.5.11 i've got a lot of database errors.
How to reproduce?
upgrade from 1.5.10 to 1.5.11
Configuration file(s) (yaml or .env)
No response
Relevant log output
BunkerWeb version
1.5.11
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
Code of Conduct
The text was updated successfully, but these errors were encountered: