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

Changing already-assigned IP Address to FHRP group silently ignores change #5798

New Issue
Closed
opened 2025-12-29 19:32:47 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:32:47 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Dec 17, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.1

Python version

3.8

Steps to Reproduce

  1. Create an IP address; assign it to an interface
  2. Create an FHRP group
  3. Navigate to the original IP address and click Edit (i.e. go to /ipam/ip-addresses/NN/edit/)
  4. Under "Interface Assignment", notice that it's currently assigned to a device+interface
  5. Click on the "FHRP Group" tab
  6. Select the FHRP group created in step 2 above
  7. Click Save

Expected Behavior

The IP address should now be assigned to the FHRP group, instead of the interface

Observed Behavior

A green box pops up saying that the address was updated; but it is still assigned to the interface, not the FHRP group.

Workaround: When you go to the "Interface Assignment" tab, under "Device" click the (X) next to the device name and interface name to remove them, then go to the "FHRP Group" tab, then select the FHRP group.

I think what's probably happening is that the form is submitted with both device/interface and FHRP group selected, and the server silently takes just the device/interface. If so: when you make a selection under "FHRP Group" (or indeed any other tab), it should automatically deselect anything in the other tabs.

Originally created by @candlerb on GitHub (Dec 17, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.1 ### Python version 3.8 ### Steps to Reproduce 1. Create an IP address; assign it to an interface 2. Create an FHRP group 3. Navigate to the original IP address and click Edit (i.e. go to `/ipam/ip-addresses/NN/edit/`) 4. Under "Interface Assignment", notice that it's currently assigned to a device+interface 5. Click on the "FHRP Group" tab 6. Select the FHRP group created in step 2 above 7. Click Save ### Expected Behavior The IP address should now be assigned to the FHRP group, instead of the interface ### Observed Behavior A green box pops up saying that the address was updated; but it is still assigned to the interface, not the FHRP group. **Workaround:** When you go to the "Interface Assignment" tab, under "Device" click the (X) next to the device name and interface name to remove them, *then* go to the "FHRP Group" tab, *then* select the FHRP group. I think what's probably happening is that the form is submitted with *both* device/interface and FHRP group selected, and the server silently takes just the device/interface. If so: when you make a selection under "FHRP Group" (or indeed any other tab), it should automatically deselect anything in the other tabs.
adam added the type: bug label 2025-12-29 19:32:47 +01:00
adam closed this issue 2025-12-29 19:32:48 +01:00
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#5798
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?