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 number in installed module list #6343

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

Originally created by @uRhaineWork on GitHub (Apr 11, 2022).

NetBox version

v3.2.0

Python version

3.9

Steps to Reproduce

Follow steps in official tutorial on youtube from Jeremy:
https://www.youtube.com/watch?v=pIIqc31Mbwc
on creating module bay for device.

\\edit///
Added steps for reproducing this behavior:

  1. Add device 'fortigate-test'. Device role firewall, device type fortigate (without assigned template modules), site Test.
  2. From added device -> add component -> module bays -> vdom1
  3. Add module type -> vd0-root . Manufacturer Fortigate same as device.
  4. Go to Device -> module bays -> add module 'vd0-root' via green+button.

Expected Behavior

In Device -> Module bays / installed module columne i dont want to see a number in bracket. eg.:
VDom 1: vd0-root (10)

Observed Behavior

In Device -> Module bays / installed module columne, in its name field I get number in bracket that is not part of given name, it is a number of created module by 'system'. If I create 5 modules, delete them, add another 5 modules that number will count from last known created module number.

Originally created by @uRhaineWork on GitHub (Apr 11, 2022). ### NetBox version v3.2.0 ### Python version 3.9 ### Steps to Reproduce Follow steps in official tutorial on youtube from Jeremy: https://www.youtube.com/watch?v=pIIqc31Mbwc on creating module bay for device. \\\edit/// Added steps for reproducing this behavior: 1. Add device 'fortigate-test'. Device role firewall, device type fortigate (without assigned template modules), site Test. 2. From added device -> add component -> module bays -> vdom1 3. Add module type -> vd0-root . Manufacturer Fortigate same as device. 4. Go to Device -> module bays -> add module 'vd0-root' via green+button. ### Expected Behavior In Device -> Module bays / installed module columne i dont want to see a number in bracket. eg.: VDom 1: vd0-root (10) ### Observed Behavior In Device -> Module bays / installed module columne, in its name field I get number in bracket that is not part of given name, it is a number of created module by 'system'. If I create 5 modules, delete them, add another 5 modules that number will count from last known created module number.
adam closed this issue 2025-12-29 19:39:39 +01:00
adam commented 2025-12-29 19:39:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 11, 2022):

Follow steps in official tutorial on youtube from Jeremy:

The video you linked is not an official tutorial, nor does it demonstrate a stable software release. Please provide detailed written reproduction steps per the bug report template.

@jeremystretch commented on GitHub (Apr 11, 2022): > Follow steps in official tutorial on youtube from Jeremy: The video you linked is not an official tutorial, nor does it demonstrate a stable software release. Please provide detailed written reproduction steps per the bug report template.
adam commented 2025-12-29 19:39:41 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 11, 2022):

It sounds like you don't want the ID included in the module name when looking at devices. Reasonable 'feature request', maybe not a bug though.

@ghost commented on GitHub (Apr 11, 2022): It sounds like you don't want the ID included in the module name when looking at devices. Reasonable 'feature request', maybe not a bug though.
adam commented 2025-12-29 19:39:41 +01:00
Author
Owner
Copy Link

@uRhaineWork commented on GitHub (Apr 11, 2022):

  1. Add device 'fortigate-test'. Device role firewall, device type fortigate (without assigned template modules), site Test.
  2. From added device -> add component -> module bays -> vdom1
  3. Add module type -> vd0-root . Manufacturer Fortigate same as device.
  4. Go to Device -> module bays -> add module 'vd0-root' via green+button.

It sounds like you don't want the ID included in the module name when looking at devices. Reasonable 'feature request', maybe not a bug though.

Looking at youtube link, there is no ID, so I thought this is only my problem. Migrated last from v.3.1.9.

@uRhaineWork commented on GitHub (Apr 11, 2022): 1. Add device 'fortigate-test'. Device role firewall, device type fortigate (without assigned template modules), site Test. 2. From added device -> add component -> module bays -> vdom1 3. Add module type -> vd0-root . Manufacturer Fortigate same as device. 4. Go to Device -> module bays -> add module 'vd0-root' via green+button. > It sounds like you don't want the ID included in the module name when looking at devices. Reasonable 'feature request', maybe not a bug though. Looking at youtube link, there is no ID, so I thought this is only my problem. Migrated last from v.3.1.9.
adam commented 2025-12-29 19:39:41 +01:00
Author
Owner
Copy Link

@ekrichbaum commented on GitHub (Apr 11, 2022):

This may just be me, but I'm not sure that a module bay makes sense here. Virtual Domains are not a physical thing (even though FTNT charges you for them like they are) and they don't have physical modules that are assigned with them. They are more like routing-instances or vrfs and could be tracked like a vrf in the ipam portion.

I don't have any 5000s left on the network but that would be more appropriate to a module bay and module usage.

@ekrichbaum commented on GitHub (Apr 11, 2022): This may just be me, but I'm not sure that a module bay makes sense here. Virtual Domains are not a physical thing (even though FTNT charges you for them like they are) and they don't have physical modules that are assigned with them. They are more like routing-instances or vrfs and could be tracked like a vrf in the ipam portion. I don't have any 5000s left on the network but that would be more appropriate to a module bay and module usage.
adam commented 2025-12-29 19:39:41 +01:00
Author
Owner
Copy Link

@uRhaineWork commented on GitHub (Apr 12, 2022):

This may just be me, but I'm not sure that a module bay makes sense here.

In my setup its important to see where given IP/network is. Eg my prefix / prefix list has columne with custom field on which Device is pulled with this new method from 3.2.0 via Objects, showing where gateway is terminated. Going down the line my IP address / address list has additional columne with 'fortigate vdom' custom field as I need to know at glance where given IP is. This one will pull Modules.
So u pull a main Device "fortigate" into Gateway columne, and if needed FortiGate VDOM into second columne to know if its root or somewhere else. Making VDOM as phisical object wont work, as this is not true and will cause problems in racks, connections etc. I think.

@uRhaineWork commented on GitHub (Apr 12, 2022): > This may just be me, but I'm not sure that a module bay makes sense here. In my setup its important to see where given IP/network is. Eg my prefix / prefix list has columne with custom field on which Device is pulled with this new method from 3.2.0 via Objects, showing where gateway is terminated. Going down the line my IP address / address list has additional columne with 'fortigate vdom' custom field as I need to know at glance where given IP is. This one will pull Modules. So u pull a main Device "fortigate" into Gateway columne, and if needed FortiGate VDOM into second columne to know if its root or somewhere else. Making VDOM as phisical object wont work, as this is not true and will cause problems in racks, connections etc. I think.
adam commented 2025-12-29 19:39:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 12, 2022):

As @ekrichbaum points out, this is misusing the modules feature, which is intended to model physical hardware only. The number you see in parentheses is the module's unique primary key, which is sometimes needed to uniquely identify modules within a device (as modules by nature are unnamed).

I'm going to close this out as this is all expected behavior. If you'd like assistance modeling virtual domains, please consider starting a discussion to see what approaches others have taken.

@jeremystretch commented on GitHub (Apr 12, 2022): As @ekrichbaum points out, this is misusing the modules feature, which is intended to model physical hardware only. The number you see in parentheses is the module's unique primary key, which is sometimes needed to uniquely identify modules within a device (as modules by nature are unnamed). I'm going to close this out as this is all expected behavior. If you'd like assistance modeling virtual domains, please consider starting a [discussion](https://github.com/netbox-community/netbox/discussions/new) to see what approaches others have taken.
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#6343
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?