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 type dropdown lists device types when creating interfaces. #7882

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

Originally created by @kalazzawi on GitHub (Apr 8, 2023).

NetBox version

v3.4.7

Python version

3.10

Steps to Reproduce

Creating interfaces for modules (Palo Alto PA-5450 firewall chassis)

  1. create network card module bay.
  2. Add new interface component.
  3. Attempt to assign interface to module bay under the Module type dropdown.

Expected Behavior

See the list of modules for the device.

Observed Behavior

See a list of devices which is a repeat of Device type dropdown above.
netbox-bug-report-1

Originally created by @kalazzawi on GitHub (Apr 8, 2023). ### NetBox version v3.4.7 ### Python version 3.10 ### Steps to Reproduce Creating interfaces for modules (Palo Alto PA-5450 firewall chassis) 1. create network card module bay. 2. Add new interface component. 3. Attempt to assign interface to module bay under the Module type dropdown. ### Expected Behavior See the list of modules for the device. ### Observed Behavior See a list of devices which is a repeat of Device type dropdown above. ![netbox-bug-report-1](https://user-images.githubusercontent.com/17362831/230723873-70486fc4-0c02-4246-b928-a004cd0c8359.png)
adam added the type: bug label 2025-12-29 20:29:30 +01:00
adam closed this issue 2025-12-29 20:29:30 +01:00
adam commented 2025-12-29 20:29:31 +01:00
Author
Owner
Copy Link

@kalazzawi commented on GitHub (Apr 9, 2023):

I noticed when porting the data from one netbox version to another that there was a new module table. The device data was duplicated in the module table. I have since deleted all of the module table entries. However, I am not seeing how to relate it to a device (chassis). In my case, we have module bays with (module) cards in a Palo Alto PA-5450. Is there a feature planned to assign interfaces to (modules) cards and assign (module) cards to module bays with the device (chassis)?

@kalazzawi commented on GitHub (Apr 9, 2023): I noticed when porting the data from one netbox version to another that there was a new module table. The device data was duplicated in the module table. I have since deleted all of the module table entries. However, I am not seeing how to relate it to a device (chassis). In my case, we have module bays with (module) cards in a Palo Alto PA-5450. Is there a feature planned to assign interfaces to (modules) cards and assign (module) cards to module bays with the device (chassis)?
adam commented 2025-12-29 20:29:31 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Apr 9, 2023):

Your issue is not replicatable with the steps you provided. It also seems like there's a misunderstanding as to how device types and module types function in netbox.

I noticed when porting the data from one netbox version to another that there was a new module table. The device data was duplicated in the module table.

This is not something netbox has done, if you yourself have modified the database, that would explain your issues.

I would recommend reading the documentation before starting to use netbox.

https://docs.netbox.dev/en/stable/features/devices-cabling/
https://docs.netbox.dev/en/stable/features/devices-cabling/#module-types-modules
https://docs.netbox.dev/en/stable/models/dcim/module/
https://docs.netbox.dev/en/stable/models/dcim/moduletype/
https://docs.netbox.dev/en/stable/models/dcim/modulebay/

If you need further assistance, I would recommend creating a discussion post, or seeking help in our slack channel.

@kkthxbye-code commented on GitHub (Apr 9, 2023): Your issue is not replicatable with the steps you provided. It also seems like there's a misunderstanding as to how device types and module types function in netbox. > I noticed when porting the data from one netbox version to another that there was a new module table. The device data was duplicated in the module table. This is not something netbox has done, if you yourself have modified the database, that would explain your issues. I would recommend reading the documentation before starting to use netbox. https://docs.netbox.dev/en/stable/features/devices-cabling/ https://docs.netbox.dev/en/stable/features/devices-cabling/#module-types-modules https://docs.netbox.dev/en/stable/models/dcim/module/ https://docs.netbox.dev/en/stable/models/dcim/moduletype/ https://docs.netbox.dev/en/stable/models/dcim/modulebay/ If you need further assistance, I would recommend creating a discussion post, or seeking help in our slack channel.
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 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#7882
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?