Device Bulk Import: Object import failed due to object-level permissions violation #4446

Closed
opened 2025-12-29 18:36:03 +01:00 by adam · 6 comments
Owner

Originally created by @AnythingOverIP on GitHub (Jan 8, 2021).

Environment

  • Python version:
  • NetBox version: 2.10.2

When doing a bulk device import with a non-existing device type value will return the following error message: "Object import failed due to object-level permissions violation"

Steps to Reproduce

  1. Prepare an import batch (a few lines)
  2. Change one of the device_type to something that does not exist
  3. launch the import

Expected Behavior

A warning saying: Row X device_type: Object not found.

Observed Behavior

error message: Object import failed due to object-level permissions violation

This behavior is also reproducible using a non existing manufacturer. (haven't tested all columns).

Originally created by @AnythingOverIP on GitHub (Jan 8, 2021). ### Environment * Python version: * NetBox version: 2.10.2 When doing a bulk device import with a non-existing device type value will return the following error message: "Object import failed due to object-level permissions violation" ### Steps to Reproduce 1. Prepare an import batch (a few lines) 2. Change one of the device_type to something that does not exist 3. launch the import ### Expected Behavior A warning saying: Row X device_type: Object not found. <!-- What happened instead? --> ### Observed Behavior error message: Object import failed due to object-level permissions violation This behavior is also reproducible using a non existing manufacturer. (haven't tested all columns).
adam added the pending closure label 2025-12-29 18:36:03 +01:00
adam closed this issue 2025-12-29 18:36:03 +01:00
Author
Owner

@AnythingOverIP commented on GitHub (Jan 8, 2021):

Also weird: a wrong manufaturer returns "Object import failed due to object-level permissions violation", but a wrong manufacturer with a wrong rack name returns the expected warning:

  • Row 1 manufacturer: Object not found.
  • Row 1 device_type: Object not found.
  • Row 1 rack: Object not found.
@AnythingOverIP commented on GitHub (Jan 8, 2021): Also weird: a wrong manufaturer returns "Object import failed due to object-level permissions violation", but a wrong manufacturer with a wrong rack name returns the expected warning: - Row 1 manufacturer: Object not found. - Row 1 device_type: Object not found. - Row 1 rack: Object not found.
Author
Owner

@DanSheps commented on GitHub (Jan 13, 2021):

This is only on bulk import correct?

@DanSheps commented on GitHub (Jan 13, 2021): This is only on bulk import correct?
Author
Owner

@AnythingOverIP commented on GitHub (Jan 13, 2021):

@DanSheps That's the only place I witnessed it. I'm not leveraging API at the moment, so I wouldn't be able to tell you if it behaves correctly.

@AnythingOverIP commented on GitHub (Jan 13, 2021): @DanSheps That's the only place I witnessed it. I'm not leveraging API at the moment, so I wouldn't be able to tell you if it behaves correctly.
Author
Owner

@stale[bot] commented on GitHub (Mar 5, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Mar 5, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@stale[bot] commented on GitHub (Mar 21, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Mar 21, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Author
Owner

@AnythingOverIP commented on GitHub (Mar 25, 2021):

@jeremystretch Just curious, isn't this a bug?

@AnythingOverIP commented on GitHub (Mar 25, 2021): @jeremystretch Just curious, isn't this a bug?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4446