DHCP client stickiness

I have two vlans that have DHCP provided by different scopes on the Mikrotik.
I have devices that I switch between vlans for testing. A device that is moved from vlan 1 to vlan 2 is given a vlan 1 address even if I remove the lease he was given.
The only way I can fix this is to disable the dhcp scope for vlan 1 while the device boots.
At this point, the client will be sticky to the address on vlan 2, regardless of what vlan he’s placed on.

Ideas on how to really delete a lease?

Ideas on how to really delete a lease?

In most cases, you need to delete the lease on the client.

When the lease is issued, the ip of the dhcp server is sent to the client. When the client renews the lease, usually it will contact the dhcp server by its ip rather than broadcast, and request the same ip it currently has. If it is available, that dhcp server will issue it.

If the client cannot contact the dhcp server by ip, it will broadcast for an ip assignment.

At least that is the way I understand it.

edit: If you want to see the dhcp transactions in the log

/system logging
add topics=dhcp,debug action=memory

I think it was a self inflicted problem.
I saw some other strangeness and I found that I was bridging the two vlans.
I had a Cisco UCS appliance that I was using for PoE on vlan 2 and it had a dedicated management port that I assumed was out of band on vlan 1.

Removed the link for the management port and testing some more.

Thanks