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

Child location does not update when Parent location changes #6535

New Issue
Closed
opened 2025-12-29 19:42:04 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:42:04 +01:00
Owner
Copy Link

Originally created by @chadhpaine on GitHub (Jun 4, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.2.2

Python version

3.9

Steps to Reproduce

  1. Create more than one location, and populate each location with at least one rack with non-zero height of any type.
  2. Create a parent-capable device-type with non-zero height. Add a device-bay to the parent-capable device-type.
  3. Create an instance of the parent-capable device-type, and insert the device into a rack of sufficient height.
  4. Create a child-capable device-type with zero height. Then create an instance of the child-capable type.
  5. Insert the child-capable device into the rack and location of the parent-device, without a position.
  6. In the Device-Bays tab of the parent-device, associate the child-device with the open device-bay.
  7. Move the parent device into a rack of sufficient height in some other location.

Expected Behavior

The child-device's rack and location should update according to the move associated with the parent-device.

Observed Behavior

The child-device's rack updated according to the move associated with the parent-device, but the location of the child-device remains as it was before the parent-device was moved.

Example result: The child could have assigned-Location A but be found in a rack associated with Location B.

Example impact: The child-device cannot be updated in the UI until the discrepancy between Assigned-Location and Rack-Location is resolved:

Errors: Rack - Rack A15 (A15) does not belong to location B.
Originally created by @chadhpaine on GitHub (Jun 4, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.2.2 ### Python version 3.9 ### Steps to Reproduce 1. Create more than one location, and populate each location with at least one rack with non-zero height of any type. 2. Create a parent-capable device-type with non-zero height. Add a device-bay to the parent-capable device-type. 3. Create an instance of the parent-capable device-type, and insert the device into a rack of sufficient height. 4. Create a child-capable device-type with zero height. Then create an instance of the child-capable type. 5. Insert the child-capable device into the rack and location of the parent-device, without a position. 6. In the Device-Bays tab of the parent-device, associate the child-device with the open device-bay. 7. Move the parent device into a rack of sufficient height in some other location. ### Expected Behavior The child-device's rack and location should update according to the move associated with the parent-device. ### Observed Behavior The child-device's rack updated according to the move associated with the parent-device, but the location of the child-device remains as it was before the parent-device was moved. Example result: The child could have assigned-Location A but be found in a rack associated with Location B. Example impact: The child-device cannot be updated in the UI until the discrepancy between Assigned-Location and Rack-Location is resolved: ``` Errors: Rack - Rack A15 (A15) does not belong to location B. ```
adam added the type: bugstatus: accepted labels 2025-12-29 19:42:04 +01:00
adam closed this issue 2025-12-29 19:42:05 +01:00
adam commented 2025-12-29 19:42:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 3, 2022):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 3, 2022): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:42:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2022):

This may be a use case for #9903 (available in v3.3).

@jeremystretch commented on GitHub (Aug 3, 2022): This may be a use case for #9903 (available in v3.3).
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#6535
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?