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

Changing module bay to existing module doesn't update module's component. #9253

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

Originally created by @francesco-noc on GitHub (Feb 15, 2024).

Deployment Type

Self-hosted

NetBox Version

v.3.7.0

Python Version

3.11

Steps to Reproduce

  1. Create a device based on a device type having module bays (es ProCurve 5304xl)
  2. Create a module with components whose names depend on the module bay (es. HP 4-Port 10GbE CX4 ZL) assigned to the previously created device.
  3. Edit the module by changing the module bay.

Expected Behavior

Module components are renamed according to new module bay.
es.
Changing slot A to slot B
Interface A1 becomes B1

Observed Behavior

Module components do not change name.
es.
Changing slot A to slot B
Interface A1 remains A1

Originally created by @francesco-noc on GitHub (Feb 15, 2024). ### Deployment Type Self-hosted ### NetBox Version v.3.7.0 ### Python Version 3.11 ### Steps to Reproduce 1. Create a device based on a device type having module bays (es [ProCurve 5304xl](https://github.com/netbox-community/devicetype-library/blob/master/device-types/HPE/ProCurve-5304xl.yaml)) 2. Create a module with components whose names depend on the module bay (es. [HP 4-Port 10GbE CX4 ZL](https://github.com/netbox-community/devicetype-library/blob/master/module-types/HPE/J8708A.yaml)) assigned to the previously created device. 3. Edit the module by changing the module bay. ### Expected Behavior Module components are renamed according to new module bay. _es. Changing slot A to slot B Interface A1 becomes B1_ ### Observed Behavior Module components do not change name. _es. Changing slot A to slot B Interface A1 remains A1_
adam closed this issue 2025-12-29 20:47:31 +01:00
adam commented 2025-12-29 20:47:32 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Feb 16, 2024):

I was working on this feature because we have to manage about 3,000 devices with more than 2,000 modules and therefore we desperately need it.

This is my implementation that fix this issue's behaviour and also the proposed feature.

@francesco-noc commented on GitHub (Feb 16, 2024): I was working on [this feature](https://github.com/netbox-community/netbox/issues/13779) because we have to manage about 3,000 devices with more than 2,000 modules and therefore we desperately need it. [This](https://github.com/netbox-community/netbox/compare/develop...francesco-noc:netbox:13779-change-device-to-module) is my implementation that fix this issue's behaviour and also the proposed feature.
adam commented 2025-12-29 20:47:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2024):

Module components do not change name

Of course they don't; there is no mechanism in place to enable this. The name template defined for the component type is available only when creating a new component. There is no logic in place to facilitate modifying the name of an existing component. You're welcome to submit a feature request if you'd like to propose a detailed, feasible implementation.

@jeremystretch commented on GitHub (Feb 20, 2024): > Module components do not change name Of course they don't; there is no mechanism in place to enable this. The name template defined for the component _type_ is available only when creating a new component. There is no logic in place to facilitate modifying the name of an existing component. 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 propose a detailed, feasible implementation.
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#9253
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?