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 when Multiple object custom field is selected in Table configuration #8815

Closed
bT0mm opened this issue Mar 7, 2022 · 0 comments
Assignees
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@bT0mm
Copy link

bT0mm commented Mar 7, 2022

NetBox version

v3.2.0-beta1

Python version

3.8

Steps to Reproduce

I did this on beta-demo.netbox.dev on 2022-03-07 on prefix 10.112.128.0/28

  1. Create custom field with assigned model 'ipam | prefix', type 'multiple objects', 'object type' is 'DCIM | device'
  2. Go to IPAM, Prefixes, edit a Prefix, add two objects (devices) on created custom field, save
  3. Go to IPAM, Prefixes, Configure Table, add created custom filed in selected columns, Save
  4. Refresh page

Expected Behavior

Every objects should be displayed, similar to what is shown on VLAN table with multiple Prefixes

Observed Behavior

Server Error

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

The complete exception is provided below:

<class 'TypeError'>

sequence item 0: expected str instance, int found

Python version: 3.8.10
NetBox version: 3.2.0-beta1

@bT0mm bT0mm added the type: bug A confirmed report of unexpected behavior in the application label Mar 7, 2022
@jeremystretch jeremystretch added the beta Concerns a bug/feature in a beta release label Mar 7, 2022
@jeremystretch jeremystretch self-assigned this Mar 7, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Mar 7, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants