starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Assign FHRP Group "Group" dropdown limited to ~50 entries #7920

New Issue
Closed
opened 2025-12-29 20:29:59 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:29:59 +01:00
Owner
Copy Link

Originally created by @moobys on GitHub (Apr 18, 2023).

NetBox version

v3.4.8

Python version

3.8

Steps to Reproduce

  1. Create 52+ FHRP groups
  2. Try to assign FHRP group to interface

Expected Behavior

All FHRP groups should be listed in the drop down

Observed Behavior

FHRP group drop down will cut off at about 50 in the list and not display all FHRP groups

Originally created by @moobys on GitHub (Apr 18, 2023). ### NetBox version v3.4.8 ### Python version 3.8 ### Steps to Reproduce 1. Create 52+ FHRP groups 2. Try to assign FHRP group to interface ### Expected Behavior All FHRP groups should be listed in the drop down ### Observed Behavior FHRP group drop down will cut off at about 50 in the list and not display all FHRP groups
adam added the type: bug label 2025-12-29 20:29:59 +01:00
adam closed this issue 2025-12-29 20:29:59 +01:00
adam commented 2025-12-29 20:29:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2023):

I'm not able to reproduce this on v3.4.8. After creating 100 FHRP groups, they all appear in the list of available groups when attempting to assign one to an interface.

It's likely that something is preventing the second API call from succeeding when you reach the end of the list. See if you can employ your browser's developer tools to determine whether the second API call is being made, and if so what the response is.

@jeremystretch commented on GitHub (Apr 19, 2023): I'm not able to reproduce this on v3.4.8. After creating 100 FHRP groups, they all appear in the list of available groups when attempting to assign one to an interface. It's likely that something is preventing the second API call from succeeding when you reach the end of the list. See if you can employ your browser's developer tools to determine whether the second API call is being made, and if so what the response is.
adam commented 2025-12-29 20:30:00 +01:00
Author
Owner
Copy Link

@moobys commented on GitHub (Apr 25, 2023):

I was able to recreate this today. I have 50+ FHRP groups and a switch with
50+ SVI virtual vlan interfaces but I don't think it is the FHRP group
quantity as much as group IDs above 200.
If I have an IP address assigned to the vlan interface first, then select
'assign FHRP group', only the FHRP group with an IP in the same subnet
appears.
If I do not have an IP address assigned to the vlan interface first, and
select 'assign FHRP group', all FHRP groups with group ID <200 appear, but
not the higher group IDs. This was my issue as I was trying to assign FHRP
groups with group IDs in the 200-255 range.

I was able to assign IPs to the interfaces first and then the FHRP group
(greater than 200) to the interface, so I'm not sure it's an issue now,

@moobys commented on GitHub (Apr 25, 2023): I was able to recreate this today. I have 50+ FHRP groups and a switch with 50+ SVI virtual vlan interfaces but I don't think it is the FHRP group quantity as much as group IDs above 200. If I have an IP address assigned to the vlan interface first, then select 'assign FHRP group', only the FHRP group with an IP in the same subnet appears. If I do not have an IP address assigned to the vlan interface first, and select 'assign FHRP group', all FHRP groups with group ID <200 appear, but not the higher group IDs. This was my issue as I was trying to assign FHRP groups with group IDs in the 200-255 range. I was able to assign IPs to the interfaces first and then the FHRP group (greater than 200) to the interface, so I'm not sure it's an issue now,
adam commented 2025-12-29 20:30:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2023):

I'm going to close this out it doesn't appear any action is needed at this time. If you continue to encounter issues, we're happy to revisit this.

@jeremystretch commented on GitHub (May 2, 2023): I'm going to close this out it doesn't appear any action is needed at this time. If you continue to encounter issues, we're happy to revisit this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7920
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?