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

[gurubert]

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.

[bctiemann]

@gurubert I can't reproduce this:

Can you narrow down a reproducible case?

[gurubert]

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?

[jeremystretch]

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

[gurubert]

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.

[github-actions]

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.

[gurubert]

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

[hzc12321]

I have encountered a similar issue, but this : #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.

[gurubert]

That would explain the behaviour.

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