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

If you create a port in Alphanumeric ranges with not enough Rear ports, a server error will be displayed. #14117

Closed
penM000 opened this issue Oct 25, 2023 · 2 comments · Fixed by #14163
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@penM000
Copy link

penM000 commented Oct 25, 2023

NetBox version

v3.6.4

Python version

3.8

Steps to Reproduce

  1. Create a rear port, with position 1.
  2. When creating a front port, use Alphanumeric ranges to create a front port that is greater than or equal to the rear port.
  3. Server error is confirmed.
    image
    image

Expected Behavior

Expect that the creation process will not take place. If no rear port is selected, no creations can be made.

Observed Behavior

The create process could be performed with no available rear ports.

@penM000 penM000 added the type: bug A confirmed report of unexpected behavior in the application label Oct 25, 2023
@DanSheps
Copy link
Member

  1. Server error is confirmed.

To be clear, you would like a proper error to be displayed, not the generic Django error, correct?

The create process could be performed with no available rear ports.

It dooesn't actually create anything, it generates an erro, this is expected.

@arthanson arthanson added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Oct 26, 2023
@arthanson arthanson self-assigned this Oct 26, 2023
@penM000
Copy link
Author

penM000 commented Oct 27, 2023

To be clear, you would like a proper error to be displayed, not the generic Django error, correct?

Yes, I thought this error was not appropriate and reported it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
3 participants