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

FHRP Groups with multiple IPs can not be assigned to interface #8096

Closed
basti1508 opened this issue Dec 17, 2021 · 1 comment
Closed

FHRP Groups with multiple IPs can not be assigned to interface #8096

basti1508 opened this issue Dec 17, 2021 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@basti1508
Copy link

NetBox version

v3.1.1

Python version

3.8

Steps to Reproduce

  1. Create FHRP Group
  2. Add IP Adresses (for this example 10 IPs)
  3. Assign FHRP Group to Interface

Expected Behavior

The FHRP Group should be assigned to the interface

Observed Behavior

The Group could not be assiged. It may be better to use show/use the ID or a unique description there.

<class 'django.db.utils.DataError'>

value too long for type character varying(200)


Python version: 3.8.10
NetBox version: 3.1.1
@basti1508 basti1508 added the type: bug A confirmed report of unexpected behavior in the application label Dec 17, 2021
@jeremystretch
Copy link
Member

There are two issues here:

  1. The string representation of an FHRPGroup should not include all assigned IP addresses.
  2. The exception is raised because the string representation of the FHRPGroup exceeds the maximum allowed size of the object_repr field in the ObjectChange model.

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Dec 18, 2021
@jeremystretch jeremystretch self-assigned this Dec 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants