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

Modules with Frontport get error in v3.2 beta 2 #6264

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

Originally created by @rodewalder on GitHub (Mar 26, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0-beta2

Python version

3.9

Steps to Reproduce

  1. Create a Module Type with Rear and Front ports
  2. Add a module in a device module bay
  3. Click create and you get "<class 'dcim.models.device_components.RearPort.DoesNotExist'>"

Expected Behavior

The module create work with rear and front port. I use it for modular patchboxes.

Observed Behavior

Module Types with interface or only rear ports work, but if a module type has front port it fails

Originally created by @rodewalder on GitHub (Mar 26, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0-beta2 ### Python version 3.9 ### Steps to Reproduce 1. Create a Module Type with Rear and Front ports 2. Add a module in a device module bay 3. Click create and you get "<class 'dcim.models.device_components.RearPort.DoesNotExist'>" ### Expected Behavior The module create work with rear and front port. I use it for modular patchboxes. ### Observed Behavior Module Types with interface or only rear ports work, but if a module type has front port it fails
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:38:41 +01:00
adam closed this issue 2025-12-29 19:38:41 +01:00
adam commented 2025-12-29 19:38:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 28, 2022):

I'm not able to reproduce this on the current feature branch. It's possible that the bug has been resolved inadvertently in a recent change. If you are still able to reproduce the issue, please update your post above to include exact reproduction instructions.

@jeremystretch commented on GitHub (Mar 28, 2022): I'm not able to reproduce this on the current `feature` branch. It's possible that the bug has been resolved inadvertently in a recent change. If you are still able to reproduce the issue, please update your post above to include **exact** reproduction instructions.
adam commented 2025-12-29 19:38:42 +01:00
Author
Owner
Copy Link

@rodewalder commented on GitHub (Mar 28, 2022):

If I use for example as rear port {module}/mpo and as frontport {module}/mpo it runs into the error.
If I use the rear port without {module} it works.
There are a problem to setup the front and resr port connection when the module will be created. The right name for the rear port is not available.

@rodewalder commented on GitHub (Mar 28, 2022): If I use for example as rear port {module}/mpo and as frontport {module}/mpo it runs into the error. If I use the rear port without {module} it works. There are a problem to setup the front and resr port connection when the module will be created. The right name for the rear port is not available.
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 beta status: accepted 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#6264
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?