starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Server Error after upgrade to 2.3.5 #1845

New Issue
Closed
opened 2025-12-29 17:19:42 +01:00 by adam · 6 comments
adam commented 2025-12-29 17:19:42 +01:00
Owner
Copy Link

Originally created by @mpatcheco on GitHub (Jul 13, 2018).

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

Originally created by @mpatcheco on GitHub (Jul 13, 2018). ### Issue type [ ] Feature request <!-- An enhancement of existing functionality --> [X] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> [ ] Housekeeping <!-- Changes pertaining to the codebase itself --> 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
adam closed this issue 2025-12-29 17:19:42 +01:00
adam commented 2025-12-29 17:19:43 +01:00
Author
Owner
Copy Link

@mpatcheco commented on GitHub (Jul 13, 2018):

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

pip3 install django-filter==1.1.0

@mpatcheco commented on GitHub (Jul 13, 2018): According to @jeremystretch a quick fix is to downgrade django-filter **pip3 install django-filter==1.1.0**
adam commented 2025-12-29 17:19:43 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Jul 14, 2018):

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.

@mmahacek commented on GitHub (Jul 14, 2018): 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.
adam commented 2025-12-29 17:19:43 +01:00
Author
Owner
Copy Link

@snazy2000 commented on GitHub (Jul 16, 2018):

Same, thanks for the fix @mpatcheco

@snazy2000 commented on GitHub (Jul 16, 2018): Same, thanks for the fix @mpatcheco
adam commented 2025-12-29 17:19:44 +01:00
Author
Owner
Copy Link

@drybjed commented on GitHub (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?

@drybjed commented on GitHub (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?
adam commented 2025-12-29 17:19:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 16, 2018):

@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.

@jeremystretch commented on GitHub (Jul 16, 2018): @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.
adam commented 2025-12-29 17:19:44 +01:00
Author
Owner
Copy Link

@drybjed commented on GitHub (Jul 16, 2018):

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

@drybjed commented on GitHub (Jul 16, 2018): @jeremystretch Excellent, thanks for quick reaction. :-)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1845
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?