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

Add Components to Module Types not working as expected? #6996

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

Originally created by @bdangus on GitHub (Sep 16, 2022).

NetBox version

V3.3.3

Python version

3.10

Steps to Reproduce

I'm reluctant to label this as a bug, because I may be doing something wrong, but I'm not sure what? In any event, here are the details...

I'm doing this all from the demo application: (https://demo.netbox.dev/)
I'm trying to add an interface component to a module type.

Create a Module Type
Choose Add Components... Interfaces
The "Add a new interface template" form appears:

  • Device type* is "-----" (I'm not sure what to put here since I don't think it's relevant in this context)
  • Module type is pre-selected based on the module type I am adding an interface to
  • I choose an interface Type (e.g. 100BASE-TX)
    If I leave Device Type* blank, I get "Device Type field is required" message underneath the Device Type field
    If I select a Device Type (just to try it), I get "A Component template cannot be associated with both a device type and a module type" message in red in the bottom right.

I also tried adding a Power Port component and ran into the same thing.

Expected Behavior

I'm expecting that I won't need to select a Device Type when adding a Component to Module Type.

Observed Behavior

I'm being forced to select a Device Type when adding a Component to Module Type. If I do, I get "A Component template cannot be associated with both a device type and a module type" message in red in the bottom right.

Originally created by @bdangus on GitHub (Sep 16, 2022). ### NetBox version V3.3.3 ### Python version 3.10 ### Steps to Reproduce I'm reluctant to label this as a bug, because I may be doing something wrong, but I'm not sure what? In any event, here are the details... I'm doing this all from the demo application: (https://demo.netbox.dev/) I'm trying to add an interface component to a module type. Create a Module Type Choose Add Components... Interfaces The "Add a new interface template" form appears: - Device type* is "-----" (I'm not sure what to put here since I don't think it's relevant in this context) - Module type is pre-selected based on the module type I am adding an interface to - I choose an interface Type (e.g. 100BASE-TX) If I leave Device Type* blank, I get "Device Type field is required" message underneath the Device Type field If I select a Device Type (just to try it), I get "A Component template cannot be associated with both a device type and a module type" message in red in the bottom right. I also tried adding a Power Port component and ran into the same thing. ### Expected Behavior I'm expecting that I won't need to select a Device Type when adding a Component to Module Type. ### Observed Behavior I'm being forced to select a Device Type when adding a Component to Module Type. If I do, I get "A Component template cannot be associated with both a device type and a module type" message in red in the bottom right.
adam added the status: duplicate label 2025-12-29 19:47:35 +01:00
adam closed this issue 2025-12-29 19:47:35 +01:00
adam commented 2025-12-29 19:47:36 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Sep 16, 2022):

Duplicate of https://github.com/netbox-community/netbox/issues/10383

It is fixed and will be in the next release.

@kkthxbye-code commented on GitHub (Sep 16, 2022): Duplicate of https://github.com/netbox-community/netbox/issues/10383 It is fixed and will be in the next release.
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 status: duplicate
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#6996
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?