Using OMAPI to release a DHCP lease on a failover pair

[Isaiah Olson]

Hello,

I am having some issues getting the OMAPI method for setting a lease to the
released state to work, in order to allow a new client to get the lease. The
servers in question are in a failover pair. The guidance that I have seen
recommends to do the following to manually release a lease on the server
side via OMAPI:

server x.x.x.x
port 7911
key omapi_key (key)
connect
new lease
set ip-address = 1.1.1.1
open
set state = 4
update

In this case, the pool contains only a single address, and it doesn't seem
to work whether I make the change on the just the primary or both the
primary and secondary. In either case, I get the following logs (with the
exception of the state change on the secondary when I have tried not making
any change there):

Primary:
Jul 30 14:02:54 loc3 dhcpd[25263]: lease 1.1.1.1 state changed from active
to released
Jul 30 14:02:58 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: network 1.1.1.0/31: no free leases
Jul 30 14:03:01 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: network 1.1.1.0/31: no free leases
Jul 30 14:03:04 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: network 1.1.1.0/31: no free leases
Jul 30 14:03:07 loc3 dhcpd[25263]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: network 1.1.1.0/31: no free leases

Secondary:
Jul 30 14:02:55 loc36 dhcpd[19842]: lease 1.1.1.1 state changed from free to
released
Jul 30 14:02:58 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: peer holds all free leases
Jul 30 14:03:01 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: peer holds all free leases
Jul 30 14:03:04 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: peer holds all free leases
Jul 30 14:03:07 loc36 dhcpd[19842]: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via
1.1.1.0: peer holds all free leases

The pre-existing lease was for a different MAC address than
aa:bb:cc:dd:ee:ff. The device with the old MAC address is still the only one
that is able to get a new lease, even after releasing that lease via OMAPI.
Any guidance on how to get this to work in this case would be appreciated. I
am not sure if the existence of the failover configuration is the cause of
the issue, or if there is another reason for this behavior, but there don't
seem to be any errors or any other info returned by OMAPI which indicate why
this might be happening.

Thanks,
Isaiah