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

Editing Module's ModuleBay assignment doens't affect module's components #8644

New Issue
Closed
opened 2025-12-29 20:39:17 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:39:17 +01:00
Owner
Copy Link

Originally created by @francesco-noc on GitHub (Sep 19, 2023).

NetBox version

v3.6.1

Python version

3.11

Steps to Reproduce

  1. Create a Device instance of a DeviceType with more than one equal ModuleBay (e.g. HPE Aruba 2930M-48G-POE+).
  2. Create a Module instance of a ModuleType with components whose name include {module} (e.g. Aruba X372 1050W AC Power Supply).
  3. Create a second Module instance of a ModuleType with components whose name include {module} (e.g. Aruba X372 1050W AC Power Supply).
  4. Delete first Module instance.
  5. Edit second Module changing associated ModuleBay from second to first.

Expected Behavior

The Module's component name changes according to ModuleBay position.

e.g. Power Port name changes from PS 2 to PS 1.

Observed Behavior

The Module's component name doesn't change according to ModuleBay position.

Originally created by @francesco-noc on GitHub (Sep 19, 2023). ### NetBox version v3.6.1 ### Python version 3.11 ### Steps to Reproduce 0) Create a Device instance of a DeviceType with more than one equal ModuleBay (e.g. HPE Aruba 2930M-48G-POE+). 1) Create a Module instance of a ModuleType with components whose name include {module} (e.g. Aruba X372 1050W AC Power Supply). 2) Create a second Module instance of a ModuleType with components whose name include {module} (e.g. Aruba X372 1050W AC Power Supply). 3) Delete first Module instance. 4) Edit second Module changing associated ModuleBay from second to first. ### Expected Behavior The Module's component name changes according to ModuleBay position. e.g. Power Port name changes from PS 2 to PS 1. ### Observed Behavior The Module's component name doesn't change according to ModuleBay position.
adam closed this issue 2025-12-29 20:39:17 +01:00
adam commented 2025-12-29 20:39:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 19, 2023):

This is expected behavior. Component names are derived automatically only upon creation; there is no logic in NetBox to rename components retroactively, as this could be dangerous. However, you're welcome to submit a feature request if you'd like to write up a proposal.

@jeremystretch commented on GitHub (Sep 19, 2023): This is expected behavior. Component names are derived automatically only upon creation; there is no logic in NetBox to rename components retroactively, as this could be dangerous. However, you're welcome to submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&projects=&template=feature_request.yaml) if you'd like to write up a proposal.
adam commented 2025-12-29 20:39:17 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Sep 20, 2023):

Thanks for the quick reply. I have thought of a real case where the position of a module is changed and therefore the names of the associated interfaces or power ports should change accordingly. Perhaps I only have this case in mind and not others, so why could this be dangerous? What problem could occur? I ask this to consider writing a proposal. Thanks again.

@francesco-noc commented on GitHub (Sep 20, 2023): Thanks for the quick reply. I have thought of a real case where the position of a module is changed and therefore the names of the associated interfaces or power ports should change accordingly. Perhaps I only have this case in mind and not others, so why could this be dangerous? What problem could occur? I ask this to consider writing a proposal. Thanks again.
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
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#8644
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?