-
-
Notifications
You must be signed in to change notification settings - Fork 71
Bug when launching mass upgrade operation #254
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
Comments
The field |
Another odd thing is when I looked at the firmware build just before deleting it, there were entries for two binaries there, the current one and the old one I thought I had deleted (although it was "blank"). So I'm unsure if the deletion actually cleared out the entry for that binary. Maybe it deleted the file, but not the entry, if that makes sense? |
I cannot replicate this issue. While trying to replicate this issue, I found other bugs though, so I am finding areas for improvement, but we need to provide precise instructions which allow to replicate the bug in the development env to fix them. Feel free to reopen the bug report if you can still reproduce it on master, here's the instructions for the development installation: |
Tried to create a mass upgrade operation. On the firmware object I had previously added a build, deleted it then added a new binary. Upon clicking Launch Mass Upgrade I got the 500 error, and found this in the openwisp2.log
The text was updated successfully, but these errors were encountered: