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

new FHRP group assignment does not work, group dropdown is empty #10789

New Issue
Closed
opened 2025-12-29 21:35:57 +01:00 by adam · 9 comments
adam commented 2025-12-29 21:35:57 +01:00
Owner
Copy Link

Originally created by @gurubert on GitHub (Feb 21, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.2.2

Python Version

3.11

Steps to Reproduce

  1. Create an interface
  2. Create a FHRP group
  3. Go to the interface and try to assign the FHRP group

Expected Behavior

The group dropdown in "Add a new FHRP group assignment" is filled with the available FHRP groups.

Observed Behavior

In the form "Add a new FHRP group assignment" the group dropdown is empty.

Originally created by @gurubert on GitHub (Feb 21, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.2.2 ### Python Version 3.11 ### Steps to Reproduce 1. Create an interface 2. Create a FHRP group 3. Go to the interface and try to assign the FHRP group ### Expected Behavior The group dropdown in "Add a new FHRP group assignment" is filled with the available FHRP groups. ### Observed Behavior In the form "Add a new FHRP group assignment" the group dropdown is empty.
adam added the type: bug label 2025-12-29 21:35:57 +01:00
adam closed this issue 2025-12-29 21:35:57 +01:00
adam commented 2025-12-29 21:35:57 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Feb 21, 2025):

@gurubert I can't reproduce this:

Image

Can you narrow down a reproducible case?

@bctiemann commented on GitHub (Feb 21, 2025): @gurubert I can't reproduce this: <img width="1024" alt="Image" src="https://github.com/user-attachments/assets/a6bc7f04-0c79-4dd3-9ec7-4e22460ee561" /> Can you narrow down a reproducible case?
adam commented 2025-12-29 21:35:58 +01:00
Author
Owner
Copy Link

@gurubert commented on GitHub (Feb 21, 2025):

In a test instance with 4.1.1 there is no issue assigning FHRP groups to interface.

Is there a debug mode than can be enabled?

@gurubert commented on GitHub (Feb 21, 2025): In a test instance with 4.1.1 there is no issue assigning FHRP groups to interface. Is there a debug mode than can be enabled?
adam commented 2025-12-29 21:35:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 21, 2025):

@gurubert please make sure you're testing on the latest stable release, v4.2.3.

@jeremystretch commented on GitHub (Feb 21, 2025): @gurubert please make sure you're testing on the latest stable release, v4.2.3.
adam commented 2025-12-29 21:35:58 +01:00
Author
Owner
Copy Link

@gurubert commented on GitHub (Feb 27, 2025):

I did an update of the test instance from 4.1.1 to 4.2.4 and can assign FHRP groups.

I will now compare the databases of the two instances.

@gurubert commented on GitHub (Feb 27, 2025): I did an update of the test instance from 4.1.1 to 4.2.4 and can assign FHRP groups. I will now compare the databases of the two instances.
adam commented 2025-12-29 21:35:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 7, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Mar 7, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:35:59 +01:00
Author
Owner
Copy Link

@gurubert commented on GitHub (Mar 7, 2025):

I found a symptom:

Assigning an FHRP group works on a "normal" physical interface and also on an LAG interface.

But the dropdown to select the FHRP group is empty on a virtual interface.

We have VLANs on an LAG interface with type "Virtual" where we need to assign FHRP groups.

This is on version 4.2.4

@gurubert commented on GitHub (Mar 7, 2025): I found a symptom: Assigning an FHRP group works on a "normal" physical interface and also on an LAG interface. But the dropdown to select the FHRP group is empty on a virtual interface. We have VLANs on an LAG interface with type "Virtual" where we need to assign FHRP groups. This is on version 4.2.4
adam commented 2025-12-29 21:35:59 +01:00
Author
Owner
Copy Link

@hzc12321 commented on GitHub (Mar 12, 2025):

I have encountered a similar issue, but this : https://github.com/netbox-community/netbox/issues/8435 explained it. Seems like once the interface has an IP address assigned, only FHRP groups with a related IP address assigned are displayed as options. While this makes sense in some use case, it becomes an obstacle for certain use cases.

In my use case, the FHRP group maps between a load balanced VIP and the real IPs on the VM interfaces. Once I have the FHRP group ready, I must first assign FHRP group before assigning real IP to the interface, if not, and if the VIP and real IP do not belong to the same subnet (related), the FHRP group option will disappear.

I would suggest this behaviour to be removed, as it is not a globally applicable scenario, it brings inconvenience to other use cases while bringing convenience to certain use cases. Plus, the purpose of "Avoiding the user from having to select from hundreds of potential groups" is already achieved by allowing user to type and quick search within the column.

@hzc12321 commented on GitHub (Mar 12, 2025): I have encountered a similar issue, but this : https://github.com/netbox-community/netbox/issues/8435 explained it. Seems like once the interface has an IP address assigned, only FHRP groups with a related IP address assigned are displayed as options. While this makes sense in some use case, it becomes an obstacle for certain use cases. In my use case, the FHRP group maps between a load balanced VIP and the real IPs on the VM interfaces. Once I have the FHRP group ready, I must first assign FHRP group before assigning real IP to the interface, if not, and if the VIP and real IP do not belong to the same subnet (related), the FHRP group option will disappear. I would suggest this behaviour to be removed, as it is not a globally applicable scenario, it brings inconvenience to other use cases while bringing convenience to certain use cases. Plus, the purpose of "Avoiding the user from having to select from hundreds of potential groups" is already achieved by allowing user to type and quick search within the column.
adam commented 2025-12-29 21:35:59 +01:00
Author
Owner
Copy Link

@gurubert commented on GitHub (Mar 12, 2025):

That would explain the behaviour.

The interfaces have IP adresses from networks that do not match the IPs from the FHRP groups.

@gurubert commented on GitHub (Mar 12, 2025): That would explain the behaviour. The interfaces have IP adresses from networks that do not match the IPs from the FHRP groups.
adam commented 2025-12-29 21:35:59 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 14, 2025):

@gurubert can you please reopen this as a feature request.

@arthanson commented on GitHub (Apr 14, 2025): @gurubert can you please reopen this as a feature request.
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#10789
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?