Cannot reassign out-of-Band IP address for the parent device #11626

Closed
opened 2025-12-29 21:47:49 +01:00 by adam · 3 comments
Owner

Originally created by @Etibru on GitHub (Sep 17, 2025).

NetBox Edition

NetBox Community

NetBox Version

v4.2.7

Python Version

3.10

Steps to Reproduce

  1. Add an IP on a device Interface and select 'Make this the out-of-band IP for the device' checkbox
  2. Update this IP and change the assignment interface with another device interface ()
  3. Error : Cannot reassign out-of-Band IP address for the parent device

The bug is also present in version v4.4.1

Expected Behavior

The IP should be deallocated from the previous device and added as an OOB IP on the new one.

Observed Behavior

Image
Originally created by @Etibru on GitHub (Sep 17, 2025). ### NetBox Edition NetBox Community ### NetBox Version v4.2.7 ### Python Version 3.10 ### Steps to Reproduce 1. Add an IP on a device Interface and select 'Make this the out-of-band IP for the device' checkbox 2. Update this IP and change the assignment interface with another device interface () 3. Error : Cannot reassign out-of-Band IP address for the parent device The bug is also present in version v4.4.1 ### Expected Behavior The IP should be deallocated from the previous device and added as an OOB IP on the new one. ### Observed Behavior <img width="374" height="131" alt="Image" src="https://github.com/user-attachments/assets/fc6384e5-499c-471f-b6c2-29c1358aa987" />
adam added the type: bug label 2025-12-29 21:47:49 +01:00
adam closed this issue 2025-12-29 21:47:49 +01:00
Author
Owner

@jnovinger commented on GitHub (Sep 18, 2025):

Interesting, given the specific conditional for the OOB checkbox and the specific message, this feels potentially intentional. It happened before my time working on NetBox, so I need to investigate a little more.

In the meantime, the work around appears to be, when editing the IP address, change the interface as desired and uncheck the OOB checkbox, then save. Then edit again and re-check the OOB checkbox and save.

@jnovinger commented on GitHub (Sep 18, 2025): Interesting, given the specific conditional for the OOB checkbox and the specific message, this feels potentially intentional. It happened before my time working on NetBox, so I need to investigate a little more. In the meantime, the work around appears to be, when editing the IP address, change the interface as desired and uncheck the OOB checkbox, then save. Then edit again and re-check the OOB checkbox and save.
Author
Owner

@Etibru commented on GitHub (Sep 18, 2025):

Thank you @jnovinger, the behavior is not the same for the primary IP. When the Primary IP box is checked, the interface selection is blocked. The same should be done for OOB ;)

@Etibru commented on GitHub (Sep 18, 2025): Thank you @jnovinger, the behavior is not the same for the primary IP. When the Primary IP box is checked, the interface selection is blocked. The same should be done for OOB ;)
Author
Owner

@jeremystretch commented on GitHub (Sep 29, 2025):

this feels potentially intentional

IIRC this is intentional, and addresses two issues:

  1. It prevents the accidental reassignment of the out-of-band management IP address.
  2. It solves for some chicken-and-egg challenges around the OOB IP validation. (The OOB IP must be assigned to an interface on the device before the device can elect it as its OOB IP.)
@jeremystretch commented on GitHub (Sep 29, 2025): > this feels potentially intentional IIRC this is intentional, and addresses two issues: 1. It prevents the accidental reassignment of the out-of-band management IP address. 2. It solves for some chicken-and-egg challenges around the OOB IP validation. (The OOB IP must be assigned to an interface on the device before the device can elect it as its OOB IP.)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11626