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

Module Bulk Import: Server error page comes up if data is incorrect #7436

New Issue
Closed
opened 2025-12-29 20:23:28 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:23:28 +01:00
Owner
Copy Link

Originally created by @dg2assassin on GitHub (Dec 30, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.4.1

Python version

3.8

Steps to Reproduce

  1. Navigate to "Module Bulk Import" page (/dcim/modules/import/)
  2. In the text box, add the following top line: "device,module_bay,module_type,status"
  3. In the text box, add the following second line: "non-device,slot 2,Micro 2000,active"
  4. Ensure the 'non-device' field does not match a device name that exists in NetBox
  5. Click 'submit'
  6. Observe how a 'Server Error' page comes up

net
net2

Expected Behavior

If an issue exists with the inputted data, the page should direct the user to where the issue exists. In the provided example, the issue would be in row 1, column 1. This should be shown to the user to instead of failing. This would align it with other bulk import pages. This issue seems to exist with all fields that uses netbox stored data such as module_bay and module_type.

Example from the device import page of expected behavior:

net3

Observed Behavior

If inputted data is incorrect, a server error page pulls up instead of telling the user where the issue is. This leads to frustration on which line is causing the issue.

Originally created by @dg2assassin on GitHub (Dec 30, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.4.1 ### Python version 3.8 ### Steps to Reproduce 1. Navigate to "Module Bulk Import" page (/dcim/modules/import/) 2. In the text box, add the following top line: "device,module_bay,module_type,status" 3. In the text box, add the following second line: "_non-device_,slot 2,Micro 2000,active" 4. Ensure the 'non-device' field does not match a device name that exists in NetBox 5. Click 'submit' 6. Observe how a 'Server Error' page comes up ![net](https://user-images.githubusercontent.com/25205963/210086744-e548d2d4-7f24-472d-8ad8-d9f6eddaab8c.PNG) ![net2](https://user-images.githubusercontent.com/25205963/210086754-3f2efdf4-bec7-44bf-9fa5-4ddeb567a8eb.PNG) ### Expected Behavior If an issue exists with the inputted data, the page should direct the user to where the issue exists. In the provided example, the issue would be in row 1, column 1. This should be shown to the user to instead of failing. This would align it with other bulk import pages. This issue seems to exist with all fields that uses netbox stored data such as module_bay and module_type. Example from the device import page of expected behavior: ![net3](https://user-images.githubusercontent.com/25205963/210087392-3dbe8db7-cc64-4088-8bd5-32d681dca074.PNG) ### Observed Behavior If inputted data is incorrect, a server error page pulls up instead of telling the user where the issue is. This leads to frustration on which line is causing the issue.
adam added the type: bugstatus: accepted labels 2025-12-29 20:23:28 +01:00
adam closed this issue 2025-12-29 20:23:29 +01:00
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 status: accepted type: bug
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#7436
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?