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

Port speed and upstream speed dropdowns don't work when adding circuit termination if a termination type has been selected first #18443

Open
pgnuta opened this issue Jan 21, 2025 · 2 comments
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application

Comments

@pgnuta
Copy link
Contributor

pgnuta commented Jan 21, 2025

Deployment Type

Self-hosted

NetBox Version

v4.2.2

Python Version

3.12

Steps to Reproduce

  1. Create a circuit
  2. Add a circuit termination, select any of the "termination type" options from the dropdown
  3. Use the "Port Speed" dropdown and select any option.

Expected Behavior

The numeric port speed is entered into the appropriate Port Speed or Upstream Speed box

Observed Behavior

The page either:

  • Resets to the top of the page
  • Opens a new browser tab
    In either case the expect numeric speed is not populated into the Port Speed box.

It is noted however, if the Port Speed dropdown is used before the "termination type" is selected, then the speed values in the boxes are not erased. But they cannot subsequently be changed by using the speed dropdowns after the "termination type" is selected.

In all cases manually typing values into the speed boxes still works as expected.

@pgnuta pgnuta added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 21, 2025
@DanSheps
Copy link
Member

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.2.2. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@DanSheps DanSheps added status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 21, 2025
@pgnuta
Copy link
Contributor Author

pgnuta commented Jan 21, 2025

I have re-tested this issue on a clean v4.2.2 install on docker this morning and was able to reproduce the issue. No changes to the steps to reproduce are required except the obvious prerequisite existence of the circuit type and circuit provider objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants