-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
Is this urgent?
No
How are you running netbox-ssot?
Podman
Which version of netbox are you using
v4.2.4
Which version of netbox-ssot are you running
v1.11.6
Which module has the issue?
General (not module-specific)
Share your configuration
I believe this bug does not relate to my configuration.What is the problem?
When a NetBox IP-address is assigned to a NetBox FHRP Group, netbox-ssot will error when fetching IP-addresses from NetBox.
Steps to reproduce
- Create a NetBox FHRP Group (i.e. Protocol: VRRPv3, Group ID: 1)
- Create a NetBox IP-address and assign it to said FHRP Group (i.e. address: 1.1.1.1/24, FHRP Group: VRRPv3: 1)
- Run netbox-ssot
What did you expect to happen?
I expected that netbox-ssot accounted for FHRP groups.
What actually happened?
Netbox-ssot stopped running with an ERROR-output
Share DEBUG-level logs (remove sensitive information)
A summarized output of the DEBUG log:
2025/06/26 14:18:44 rest.go:104 DEBUG (inventory): Successfully received all objects.IPAddress: [
...
...
...
2025/06/26 14:18:44 main.go:69 ERROR (main): get index values for ip address: unsupported assigned object type for ip address IPAddress{ID: 8853, Address: 1.1.1.1/24, Status: active, DNSName: }: : initIPAddresses
The NetBox API displays the FHRP-group like the following example:
"assigned_object_type": "ipam.fhrpgroup",
"assigned_object_id": 1,
"assigned_object": {
"id": 1,
"url": "https://netbox.example.com/api/ipam/fhrp-groups/1/",
"display": "VRRPv3: 1 (1.1.1.1/24)",
"protocol": "vrrp3",
"group_id": 1,
"description": ""
},
Share your environment details
# hostnamectl
Virtualization: vmware
Operating System: Rocky Linux 8.10 (Green Obsidian)
CPE OS Name: cpe:/o:rocky:rocky:8:GA
Kernel: Linux 4.18.0-553.40.1.el8_10.x86_64
Architecture: x86-64
# podman -v
podman version 4.9.4-rhel
Metadata
Metadata
Assignees
Labels
No labels