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

Unable to assign device bay to tenant #331

New Issue
Closed
opened 2025-12-29 16:20:59 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:20:59 +01:00
Owner
Copy Link

Originally created by @Gelob on GitHub (Aug 5, 2016).

When trying to assign a device bay to a tenant we get the following error. This happens even if the parent device is not set to anything.

screen shot 2016-08-05 at 1 05 05 pm

However, we would like the functionality of being able to assign a device/chassis to one Tenant and then assign device bays to a different tenant.

Originally created by @Gelob on GitHub (Aug 5, 2016). When trying to assign a device bay to a tenant we get the following error. This happens even if the parent device is not set to anything. ![screen shot 2016-08-05 at 1 05 05 pm](https://cloud.githubusercontent.com/assets/422752/17446140/77e7562c-5b0d-11e6-8766-813de8d103c2.png) However, we would like the functionality of being able to assign a device/chassis to one Tenant and then assign device bays to a different tenant.
adam added the type: bug label 2025-12-29 16:20:59 +01:00
adam closed this issue 2025-12-29 16:20:59 +01:00
adam commented 2025-12-29 16:21:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 5, 2016):

Individual device bays can't be assigned to tenants; only devices can. What steps did you take to trigger that error?

@jeremystretch commented on GitHub (Aug 5, 2016): Individual device bays can't be assigned to tenants; only devices can. What steps did you take to trigger that error?
adam commented 2025-12-29 16:21:00 +01:00
Author
Owner
Copy Link

@csfreak commented on GitHub (Aug 7, 2016):

FWIW, I have lots of situations where it makes sense for device bays to have a different tenant than the parent device. Most common occurrence is Blade Servers and Blade Chassis. The Chassis always belongs to our IT "tenant", but individual servers can belong to any "tenant".

@csfreak commented on GitHub (Aug 7, 2016): FWIW, I have lots of situations where it makes sense for device bays to have a different tenant than the parent device. Most common occurrence is Blade Servers and Blade Chassis. The Chassis always belongs to our IT "tenant", but individual servers can belong to any "tenant".
adam commented 2025-12-29 16:21:00 +01:00
Author
Owner
Copy Link

@Gelob commented on GitHub (Aug 8, 2016):

@jeremystretch I went to Devices > picked a device with device bays > then clicked on the name of one of the device bays which brought me to its device page, then clicked edit this device and attempted to change the tenant field.

@Gelob commented on GitHub (Aug 8, 2016): @jeremystretch I went to Devices > picked a device with device bays > then clicked on the name of one of the device bays which brought me to its device page, then clicked edit this device and attempted to change the tenant field.
adam commented 2025-12-29 16:21:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2016):

I think it might help to clarify some terminology. There are three components relevant here:

  • Parent device
  • Device bay
  • Child device

Both parent and child devices can belong to any tenant (or no tenant) independent of each other. Device bays within a parent device have no tenant assignment capability. So you can't say "Slot 1 of this device is reserved for Tenant A," but you can say "The device installed in slot 1 belongs to Tenant A."

@jeremystretch commented on GitHub (Aug 8, 2016): I think it might help to clarify some terminology. There are three components relevant here: - Parent device - Device bay - Child device Both parent and child devices can belong to any tenant (or no tenant) independent of each other. Device bays within a parent device have no tenant assignment capability. So you can't say "Slot 1 of this device is reserved for Tenant A," but you can say "The device installed in slot 1 belongs to Tenant A."
adam commented 2025-12-29 16:21:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2016):

This is a bug in the DeviceForm initialization for child devices; nothing specifically related to tenancy.

@jeremystretch commented on GitHub (Aug 8, 2016): This is a bug in the DeviceForm initialization for child devices; nothing specifically related to tenancy.
adam commented 2025-12-29 16:21:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2016):

Adding the text of the error for searchability:

<class 'django.utils.datastructures.MultiValueDictKeyError'>

"'site'"
@jeremystretch commented on GitHub (Aug 10, 2016): Adding the text of the error for searchability: ``` <class 'django.utils.datastructures.MultiValueDictKeyError'> "'site'" ```
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 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#331
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?