Coder Social home page Coder Social logo

Comments (4)

smutel avatar smutel commented on August 16, 2024 1

So I found more details.
In old requirements.txt, we are finding django-rq but nothing about rq.

rq 1.3.x is working with django-rq 2.2.x
rq 1.4.x is working with django-rq 2.3.x

Putting this in my variable works for netbox 2.7.x:

netbox_pip_constraints:
  # Blacklist pynacl 1.3.0 due to https://github.com/pyca/pynacl/issues/479
  - 'pynacl!=1.3.0'                                                                                 
  # Blacklist rq 1.3.0 due to https://github.com/rq/django-rq/issues/421                     
  # https://github.com/netbox-community/netbox/issues/4633                                          
  - 'rq==1.3.0'

from ansible-role-netbox.

lae avatar lae commented on August 16, 2024

See #97 (comment) and 513bd4e

You can just specify netbox_pip_constraints locally for a quick fix. CI seems to have failed on Debian Stretch only with the above commit and I haven't gotten around to looking into why yet.

from ansible-role-netbox.

smutel avatar smutel commented on August 16, 2024

Even if I set this in my variables, it does not work:

netbox_pip_constraints:                                                                             
  # Blacklist pynacl 1.3.0 due to https://github.com/pyca/pynacl/issues/479                         
  - 'pynacl!=1.3.0'                                                                                 
  # Blacklist django-rq 2.3.1 due to https://github.com/rq/django-rq/issues/421                     
  # https://github.com/netbox-community/netbox/issues/4633                                          
  - 'django-rq!=2.3.1'

This is due to the version of django-rq used in the old version of netbox.
requirements.txt need to be changed with django-rq==2.3.2 instead of django-rq==2.2.0.

The issue is the same with a fresh install of 2.7.6 for example.

from ansible-role-netbox.

lae avatar lae commented on August 16, 2024

Weird, I only tested against 2.7.12 but it seemed to work against that.

What happens if you add a constraint for rq<1.4.0 instead?

Modifying the requirements.txt file with the role is not something I'm keen on doing in this role, as it causes conflicts in git-based deployments and idempotency issues for stable deployments.

from ansible-role-netbox.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.