Skip to content
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

Server Error after upgrade to 2.3.5 #2239

Closed
mpatcheco opened this issue Jul 13, 2018 · 6 comments
Closed

Server Error after upgrade to 2.3.5 #2239

mpatcheco opened this issue Jul 13, 2018 · 6 comments

Comments

@mpatcheco
Copy link

Issue type

[ ] Feature request
[X] Bug report
[ ] Documentation
[ ] Housekeeping

After an upgrade from 2.3.1 to 2.3.4, when access main functions (Sites, Tenants, Racks, etc ..) a error is showed

**There was a problem with your request. Please contact an administrator.

The complete exception is provided below:
<class 'TypeError'>
init() got an unexpected keyword argument 'name'**

Environment

  • Python version: python34-3.4.8-1
  • NetBox version: 2.3.5

Description

A lot of users are having the same issue upgrading from 2.3.4 or even on a fresh install of a 2.3.5

Discussion link:
https://groups.google.com/forum/#!topic/netbox-discuss/h35vs7dkbRQ%5B1-25%5D

@mpatcheco
Copy link
Author

According to @jeremystretch a quick fix is to downgrade django-filter

pip3 install django-filter==1.1.0

@mmahacek
Copy link
Contributor

Bump that I had the same error after upgrading 2.3.4 to 2.3.5. Downgrading django-filter from 2.0.0 to 1.1.0 seems to have fixed it for me.

@snazy2000
Copy link
Contributor

Same, thanks for the fix @mpatcheco

@drybjed
Copy link

drybjed commented Jul 16, 2018

This issue makes the current master branch of NetBox uninstallable out of the box, at least with Python 2.7 on Debian Stretch. Any plans for fixing that, or should switch to Python3 virtualenv solve this?

@jeremystretch
Copy link
Member

@drybjed The issue is with the new release of the django-filter library; using a virtualenv (or not) won't make any difference.

I'm going to return to my earlier approach of pinning exact versions of all required libraries in requirements.txt to mitigate this issue in the future. Will push out a new release with this change today.

@drybjed
Copy link

drybjed commented Jul 16, 2018

@jeremystretch Excellent, thanks for quick reaction. :-)

lae added a commit to lae/ansible-role-netbox that referenced this issue Jul 16, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants