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

Bulk import of devices crashes the WebUI if device_type is not found and rack/location info is given #8724

Closed
empusas opened this issue Feb 23, 2022 · 0 comments
Closed

Bulk import of devices crashes the WebUI if device_type is not found and rack/location info is given #8724

empusas opened this issue Feb 23, 2022 · 0 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@empusas
Copy link

empusas commented Feb 23, 2022

NetBox version

v3.1.5

Python version

3.9

Steps to Reproduce

  1. Create a device import with an unknown device type and rack and location info.
  2. past the content into the web interface bulk import
  3. start the import

example
tenant,manufacturer,device_role,device_type,name,site,location,rack,position,face,status
lulu,Cisco,Access Switch,Cata8T-4G,Gandalf,Neverland,Room 1,14,24,front,active

Expected Behavior

A red popup error message should appear like for any other issues with the imported data.
image001

Observed Behavior

The WebUI crashes with a server error.
image002
@empusas empusas added the type: bug A confirmed report of unexpected behavior in the application label Feb 23, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Mar 4, 2022
@jeremystretch jeremystretch self-assigned this Mar 4, 2022
@jeremystretch jeremystretch mentioned this issue Mar 7, 2022
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

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
@empusas @jeremystretch