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

unable to assign FHRP group if interface has an IP address assigned #9272

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

Originally created by @lanman9000 on GitHub (Feb 20, 2024).

Deployment Type

Self-hosted

NetBox Version

3.7.2

Python Version

3.8

Steps to Reproduce

Create an FHRP group
Create a device
Create an interface on the device
Assign an IP address to the interface
Attempt to assign an FHRP group to the interface

Expected Behavior

You should see the FHRP group you created show up in the drop down list for FHRP assingments

Observed Behavior

The FHRP group assignment dropdown is empty.

If you remove the IP address from the interface, you are then able to successfully assign an FHRP group to the interface. You can then assign the IP address to the interface.
But, it seems this bug only presents itself if the interface already has an IP address assigned.

Originally created by @lanman9000 on GitHub (Feb 20, 2024). ### Deployment Type Self-hosted ### NetBox Version 3.7.2 ### Python Version 3.8 ### Steps to Reproduce Create an FHRP group Create a device Create an interface on the device Assign an IP address to the interface Attempt to assign an FHRP group to the interface ### Expected Behavior You should see the FHRP group you created show up in the drop down list for FHRP assingments ### Observed Behavior The FHRP group assignment dropdown is empty. If you remove the IP address from the interface, you are then able to successfully assign an FHRP group to the interface. You can then assign the IP address to the interface. But, it seems this bug only presents itself if the interface already has an IP address assigned.
adam closed this issue 2025-12-29 20:47:43 +01:00
adam commented 2025-12-29 20:47:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2024):

This is working as intended. Because the interface has an IP address assigned to it, NetBox returns only FHRP groups which have a related IP address assigned. For instance, if you assign the IP address 192.168.1.123/24 to the interface, an FHRP group with the IP address 192.168.1.1/24 will be listed as an option for assignment. This is done for convenience, so that the user doesn't have to search through potentially thousands of irrelevant groups.

If you add an IP address to the group created in step one in the same prefix as the IP address created in step 4, you'll see that the group is able to be assigned to the interface.

@jeremystretch commented on GitHub (Feb 20, 2024): This is working as intended. Because the interface has an IP address assigned to it, NetBox returns only FHRP groups which have a related IP address assigned. For instance, if you assign the IP address 192.168.1.123/24 to the interface, an FHRP group with the IP address 192.168.1.1/24 will be listed as an option for assignment. This is done for convenience, so that the user doesn't have to search through potentially thousands of irrelevant groups. If you add an IP address to the group created in step one in the same prefix as the IP address created in step 4, you'll see that the group is able to be assigned to the interface.
adam commented 2025-12-29 20:47:44 +01:00
Author
Owner
Copy Link

@lanman9000 commented on GitHub (Feb 20, 2024):

So why can't it also be allowed "for convenience" to add to FHRP groups in which the IP is not in the same prefix. You can certainly parse a list of FHRP groups that the in the same IP prefix and present only those in the initial clicking of the drop-down menu, but if I specifically type an FHRP group number into the filter/search box during the FHRP assignment, why can't I return those results?

Convenience works both ways.

@lanman9000 commented on GitHub (Feb 20, 2024): So why can't it also be allowed "for convenience" to add to FHRP groups in which the IP is not in the same prefix. You can certainly parse a list of FHRP groups that the in the same IP prefix and present only those in the initial clicking of the drop-down menu, but if I specifically type an FHRP group number into the filter/search box during the FHRP assignment, why can't I return those results? Convenience works both ways.
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
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#9272
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?