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

FHRP Group Assignment not possible #5987

New Issue
Closed
opened 2025-12-29 19:35:23 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:35:23 +01:00
Owner
Copy Link

Originally created by @basti1508 on GitHub (Jan 22, 2022).

NetBox version

v3.1.6

Python version

3.8

Steps to Reproduce

  1. Create an FHRP Group (eg. VRRP2, id 12)
  2. Goto Virtual Machine Interface and hit "assign FHRP Group"
  3. Group is not shown in the list

Furthermore if I assign an IP Address to the group which is not in the subnet of the VMs IP, the FHRP Group is not shown either.

Expected Behavior

It should be possible to assign an FRHP group regardless of the virtual ip address.

Observed Behavior

see above

Originally created by @basti1508 on GitHub (Jan 22, 2022). ### NetBox version v3.1.6 ### Python version 3.8 ### Steps to Reproduce 1. Create an FHRP Group (eg. VRRP2, id 12) 2. Goto Virtual Machine Interface and hit "assign FHRP Group" 3. Group is not shown in the list Furthermore if I assign an IP Address to the group which is not in the subnet of the VMs IP, the FHRP Group is not shown either. ### Expected Behavior It should be possible to assign an FRHP group regardless of the virtual ip address. ### Observed Behavior see above
adam closed this issue 2025-12-29 19:35:23 +01:00
adam commented 2025-12-29 19:35:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 24, 2022):

  1. Create an FHRP Group (eg. VRRP2, id 12)
  2. Goto Virtual Machine Interface and hit "assign FHRP Group"
  3. Group is not shown in the list

Your instructions do not reproduce the reported behavior. The group does appear if there is no IP address assigned to the interface, as expected. If there is an IP address assigned, only FHRP groups with a related IP address assigned are displayed as options. This behavior is intended, and avoids the user from having to select from hundreds of potential groups.

@jeremystretch commented on GitHub (Jan 24, 2022): > 1. Create an FHRP Group (eg. VRRP2, id 12) > 2. Goto Virtual Machine Interface and hit "assign FHRP Group" > 3. Group is not shown in the list Your instructions do not reproduce the reported behavior. The group does appear if there is no IP address assigned to the interface, as expected. If there _is_ an IP address assigned, only FHRP groups with a related IP address assigned are displayed as options. This behavior is intended, and avoids the user from having to select from hundreds of potential groups.
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#5987
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?