Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
rodewalder opened this issue Mar 26, 2022 · 2 comments
Closed

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

rodewalder opened this issue Mar 26, 2022 · 2 comments
Assignees
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@rodewalder
Copy link

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

@rodewalder rodewalder added the type: bug A confirmed report of unexpected behavior in the application label Mar 26, 2022
@rodewalder rodewalder changed the title Modules with Frontport get error Modules with Frontport get error in v3.2 beta 2 Mar 26, 2022
@jeremystretch jeremystretch added the beta Concerns a bug/feature in a beta release label Mar 28, 2022
@jeremystretch
Copy link
Member

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 jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Mar 28, 2022
@rodewalder
Copy link
Author

rodewalder commented 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.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: revisions needed This issue requires additional information to be actionable labels Mar 30, 2022
@jeremystretch jeremystretch self-assigned this Mar 31, 2022
This was referenced Apr 5, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants