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

Inactive Replicate components and Adopt components fields after installing the module in the device #8854

New Issue
Closed
opened 2025-12-29 20:42:12 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:42:12 +01:00
Owner
Copy Link

Originally created by @Breadberry07 on GitHub (Nov 20, 2023).

NetBox version

v3.6.5

Python version

3.8

Steps to Reproduce

I apologize in advance, maybe this is not a bug, but it would be cool if you could activate the "Replicate components" and "Adopt components" fields so that when you move a previously installed module to another slot on the device, the interfaces also change their number to the slot number (this behavior is relevant for all versions of 3.6+).

This is how it manifests itself:

  1. Create some device with "Slots" (in example MX960 chassis)
    image

  2. Create some modules with "interfaces" (in example MX960 MPC5 card)
    image

  3. Install this Module to Device and activate the points "Replicate components" and "Adopt components"
    image

  4. You can see how the interface numbers have been adapted to the slot number
    image

  5. Let's try to move the module to another slot of the device and see that the "Replicate components" and "Adopt components" fields cannot be activated, respectively, because of this, the module port numbering does not change
    image

Expected Behavior

It was expected that it would be possible to adapt the numbering of interfaces when transferring the module from one slot of the device to another

Observed Behavior

It is not possible to automatically change the numbering of the module interfaces after it is installed in the device

Originally created by @Breadberry07 on GitHub (Nov 20, 2023). ### NetBox version v3.6.5 ### Python version 3.8 ### Steps to Reproduce I apologize in advance, maybe this is not a bug, but it would be cool if you could activate the "Replicate components" and "Adopt components" fields so that when you move a previously installed module to another slot on the device, the interfaces also change their number to the slot number (this behavior is relevant for all versions of 3.6+). This is how it manifests itself: 1. Create some device with "Slots" (in example MX960 chassis) ![image](https://github.com/netbox-community/netbox/assets/122742913/4bcb3a3d-90b4-4982-98e9-7c6de00a7773) 2. Create some modules with "interfaces" (in example MX960 MPC5 card) ![image](https://github.com/netbox-community/netbox/assets/122742913/a9385193-99f0-412f-8460-d262625a3940) 3. Install this Module to Device and activate the points "Replicate components" and "Adopt components" ![image](https://github.com/netbox-community/netbox/assets/122742913/ecf10c5f-b431-4c81-9f8f-99a90aa696ef) 4. You can see how the interface numbers have been adapted to the slot number ![image](https://github.com/netbox-community/netbox/assets/122742913/4121dafd-8ae8-4dc9-87e9-dedfba0b1497) 5. Let's try to move the module to another slot of the device and see that the "Replicate components" and "Adopt components" fields cannot be activated, respectively, because of this, the module port numbering does not change ![image](https://github.com/netbox-community/netbox/assets/122742913/c08fcc8e-a130-40a2-94cc-3b6605fe77b5) ### Expected Behavior It was expected that it would be possible to adapt the numbering of interfaces when transferring the module from one slot of the device to another ### Observed Behavior It is not possible to automatically change the numbering of the module interfaces after it is installed in the device
adam closed this issue 2025-12-29 20:42:12 +01:00
adam commented 2025-12-29 20:42:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 28, 2023):

This would be a feature request, not a bug. You're welcome to submit one citing your proposed implementation and use case, but bear in mind doing so will involve capturing the logic to reverse engineer the templatized slot and position identifiers. This is not a trivial task, so please be sure to include your proposed solution if you decide to proceed with a feature request.

@jeremystretch commented on GitHub (Nov 28, 2023): This would be a feature request, not a bug. You're welcome to [submit one](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&projects=&template=feature_request.yaml) citing your proposed implementation and use case, but bear in mind doing so will involve capturing the logic to reverse engineer the templatized slot and position identifiers. This is not a trivial task, so please be sure to include your proposed solution if you decide to proceed with a feature request.
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#8854
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?