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

Module Bay Parent relation is partially broken #11884

New Issue
Closed
opened 2025-12-29 21:51:13 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:51:13 +01:00
Owner
Copy Link

Originally created by @BartZimmo on GitHub (Dec 3, 2025).

Originally assigned to: @jnovinger on GitHub.

NetBox Edition

NetBox Community

NetBox Version

v4.4.7

Python Version

3.12

Steps to Reproduce

  1. Create at least 2 module bays for a device.
  2. Install modules in both bays.
  3. Edit one module bay, and select the module installed in the other bay as parent.
  4. Edit the same module bay again and remove the earlier selected module to remove the parent relation.

Expected Behavior

Once the parent relation is removed, the table should be updated, and also the module info page.

Observed Behavior

Removing the parent relation does not update the table info, and you can still see the installed module is linked to the module bay of the previously selected module.

If I delete the parent module, the child module will not be deleted. -> This is as expected.

If I were to do this without first removing the parent assignment, the child module would also be deleted after a prompt.

So the function is partially broken.

Originally created by @BartZimmo on GitHub (Dec 3, 2025). Originally assigned to: @jnovinger on GitHub. ### NetBox Edition NetBox Community ### NetBox Version v4.4.7 ### Python Version 3.12 ### Steps to Reproduce 1. Create at least 2 module bays for a device. 2. Install modules in both bays. 3. Edit one module bay, and select the module installed in the other bay as parent. 4. Edit the same module bay again and remove the earlier selected module to remove the parent relation. ### Expected Behavior Once the parent relation is removed, the table should be updated, and also the module info page. ### Observed Behavior Removing the parent relation does not update the table info, and you can still see the installed module is linked to the module bay of the previously selected module. If I delete the parent module, the child module will not be deleted. -> This is as expected. If I were to do this without first removing the parent assignment, the child module would also be deleted after a prompt. So the function is partially broken.
adam added the type: bugstatus: acceptednetboxseverity: low labels 2025-12-29 21:51:13 +01:00
adam closed this issue 2025-12-29 21:51:13 +01:00
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 netbox severity: low 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#11884
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?