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.

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

Child location does not update when Parent location changes #9481

Closed
chadhpaine opened this issue Jun 4, 2022 · 2 comments · Fixed by #10246
Closed

Child location does not update when Parent location changes #9481

chadhpaine opened this issue Jun 4, 2022 · 2 comments · Fixed by #10246
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@chadhpaine
Copy link

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.
@chadhpaine chadhpaine added the type: bug A confirmed report of unexpected behavior in the application label Jun 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented 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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Aug 3, 2022
@jeremystretch
Copy link
Member

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

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Aug 3, 2022
@arthanson arthanson self-assigned this Aug 31, 2022
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Aug 31, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Sep 2, 2022
jeremystretch added a commit that referenced this issue Sep 2, 2022
…ation

#9481 update child location whem move parent
jeremystretch added a commit that referenced this issue Sep 2, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants