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

L2VPN Termination tabs inconsistency in edit mode #15091

Closed
arthanson opened this issue Feb 8, 2024 · 0 comments · Fixed by #15138
Closed

L2VPN Termination tabs inconsistency in edit mode #15091

arthanson opened this issue Feb 8, 2024 · 0 comments · Fixed by #15138
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

@arthanson
Copy link
Collaborator

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.8

Steps to Reproduce

  1. Create an L2VPN, and a Virtual Machine interface
  2. Create an L2VPN Termination - choose the 'Virtual Machine' tab and select the interface and save.
  3. Edit the L2VPN Termination

Notice both the VLAN and 'Virtual Machine' tabs are highlighted, and there is are both the VLAN and Interface selections showing below.

Monosnap Editing L2VPN termination eth0   TEST | NetBox 2024-02-08 09-25-25

Expected Behavior

Only one tab should be highlighted and only the correct field for the tab should be shown, not the fields for both tabs.

Observed Behavior

Both tabs are highlighted and fields for both tabs are shown.

@arthanson arthanson added type: bug A confirmed report of unexpected behavior in the application severity: low Does not significantly disrupt application functionality, or a workaround is available labels Feb 8, 2024
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Feb 13, 2024
@jeremystretch jeremystretch self-assigned this Feb 13, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2024
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
Development

Successfully merging a pull request may close this issue.

2 participants