ImportError exception with django-rq v2.3.1 and rq 1.4.0 #4633
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Environment
Steps to Reproduce
./manage.py migrate
either manually or automatically as part of step 2)Based on the below errors and the inclusion of
django-rq
in the traceback, I went looking through the release history ofdjango-rq
and it's dependency,rq
to see if anything stood out. The latter has seen 4 moderately sized releases since the release of NetBox v2.7.12 in December. I had a hunch that may have something to do with it, so I installedrq==1.1.0
(the most recent version at the time 2.7.12 was released) manually into my virtualenv, then attempted migrations and they worked!I'm not entirely certain what is causing the problem but downgrading
rq
definitely solved it. I think this goes back to #4198 and that NetBox releases should be pinning all requirements used in the development environment. This would've been a non-issue if the full dependency chain was frozen.It's worth noting that v1.4.0 of
rq
was released several hours before my upgrade attempt - which would explain why my previous tests of upgrading my environment (several days ago) went without any issues. It's possiblerq
v1.3.0 would work but haven't had a chance to test all the versions after 1.1.0.And to be clear, this upgrade was done using a fresh venv in an isolated/versioned folder for the v2.7.12 install. I even wiped the whole folder & venv and ran my playbook again - same results.
Expected Behavior
Migrations complete successfully.
Observed Behavior
Migration fails with output below
The text was updated successfully, but these errors were encountered: