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 interface creation error #6275

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

Originally created by @mmfreitas on GitHub (Mar 31, 2022).

NetBox version

v3.2.0-beta2

Python version

3.8

Steps to Reproduce

Reproducable in beta demo site.

  1. Navigate to router dmi01-akron-rtr01;
  2. Create interfaces "GigabitEthernet2/1/[0-3]" of type "1000BASE-T (1GE)";
  3. Add components -> Module Bay, Create "Bay 2" with position "2";
  4. Create a new Module Type -> "4PORT 1GE" and add interfaces "GigabitEthernet{module}/1/[0-3];
  5. Install the created module type on the router module bay. (Replicate components must be ticked)

Expected Behavior

image

Observed Behavior

Since the interfaces with that name already existed, netbox throws an exception. I believe that this should be the expected behaviour but it should generate a toast error instead.

Originally created by @mmfreitas on GitHub (Mar 31, 2022). ### NetBox version v3.2.0-beta2 ### Python version 3.8 ### Steps to Reproduce Reproducable in [beta demo site](https://beta-demo.netbox.dev/). 1. Navigate to router [dmi01-akron-rtr01](https://beta-demo.netbox.dev/dcim/devices/1/interfaces/); 2. Create interfaces "GigabitEthernet2/1/[0-3]" of type "1000BASE-T (1GE)"; 3. Add components -> Module Bay, Create "Bay 2" with position "2"; 4. Create a new [Module Type](https://beta-demo.netbox.dev/dcim/module-types/add/) -> "4PORT 1GE" and add interfaces "GigabitEthernet{module}/1/[0-3]; 5. Install the created module type on the router module bay. (Replicate components must be ticked) ### Expected Behavior ![image](https://user-images.githubusercontent.com/91552302/161026543-2ae64973-def4-4548-872a-79c5520d15a7.png) ### Observed Behavior Since the interfaces with that name already existed, netbox throws an exception. I believe that this should be the expected behaviour but it should generate a toast error instead.
adam added the type: bugstatus: duplicate labels 2025-12-29 19:38:50 +01:00
adam closed this issue 2025-12-29 19:38:50 +01:00
adam commented 2025-12-29 19:38:51 +01:00
Author
Owner
Copy Link

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

I'm going to close this bug as a duplicate of #9190, as that issue does not rely on demo data and has some conversation attached.

@jeremystretch commented on GitHub (May 11, 2022): I'm going to close this bug as a duplicate of #9190, as that issue does not rely on demo data and has some conversation attached.
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 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#6275
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?