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

Unable to add vlan group with single vlan #17414

Closed
oscarminus opened this issue Sep 9, 2024 · 1 comment · Fixed by #17418
Closed

Unable to add vlan group with single vlan #17414

oscarminus opened this issue Sep 9, 2024 · 1 comment · Fixed by #17418
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

@oscarminus
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.1.0

Python Version

3.11

Steps to Reproduce

  1. Add new vlan group
  2. Type "2-2,10-49" or "2,10-49"
  3. Press save

Expected Behavior

Vlan group should be created.

Observed Behavior

Error "Maximum child VID must be greater than or equal to minimum child VID ([2, 2])" is raised.

@oscarminus oscarminus added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Sep 9, 2024
@oscarminus
Copy link
Author

Could be fixed in netbox/ipam/models/vlans.py by changing '>=' to '>' in line 103.

@arthanson arthanson added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Sep 9, 2024
@arthanson arthanson self-assigned this Sep 9, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 10, 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