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.

Sign up for GitHub

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

Jump to bottom

2.5b1 Migration of RackRole Failed #2575

Closed
mmahacek opened this issue Nov 8, 2018 · 1 comment
Closed

2.5b1 Migration of RackRole Failed #2575

mmahacek opened this issue Nov 8, 2018 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@mmahacek
Copy link
Contributor

mmahacek commented Nov 8, 2018

Environment

  • Python version: 3.6
  • NetBox version: 2.5 beta 1

Steps to Reproduce

Access /dcim/rack-roles page

Expected Behavior

The Rack Roles page should load. I checked my 2.4.7 server, and the page loads properly. On my test servers (which was a VM clone of production), there is an error when accessing the page.

Observed Behavior

<class 'ValueError'>

table data is of type <class 'dcim.models.RackRole'> but <class 'dcim.models.RackGroup'> is specified in Table.Meta.model
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation beta labels Nov 9, 2018
@jeremystretch
Copy link
Member

Wow. This has been wrong for over two years. It's just never been a problem since the RackRole and RackGroup models are so similar. Looks like a validation check was added in a more recent release of django-tables2.

@jeremystretch jeremystretch removed the beta label Nov 9, 2018
@jeremystretch jeremystretch mentioned this issue Nov 20, 2018
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jeremystretch @mmahacek