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

Assigning duplicate FHRP group to interface results in Integrity Error #15029

Closed
arthanson opened this issue Feb 2, 2024 · 0 comments · Fixed by #15047
Closed

Assigning duplicate FHRP group to interface results in Integrity Error #15029

arthanson opened this issue Feb 2, 2024 · 0 comments · Fixed by #15047
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.1

Python Version

3.8

Steps to Reproduce

View an interface
Click "Assign Group" for FHRP
Input "Group" and "Priority"
Click "Create & Add Another"
Input the same "Group" and a "Priority"
Error

IntegrityError at /ipam/fhrp-group-assignments/add/
duplicate key value violates unique constraint "ipam_fhrpgroupassignment_unique_interface_group"

Expected Behavior

Should show "duplicate assignment" on edit form

Observed Behavior

IntegrityError was thrown.

@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 2, 2024
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Feb 2, 2024
@arthanson arthanson self-assigned this Feb 5, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Feb 5, 2024
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Feb 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