Static IP not so static

[no_connection]

Had a fun thing happen with 9.3 STABLE
We used FN in a VM for our LAB today (ESXi).

One NIC for MGMT (em0) and one for client (em1). Both on separate subnets. Worked fine.
After adding a DHCP server to the MGMT net so we didn't need to set static IPs for our computers, I could no longer connect to FN.
I could not figure out what was wrong as I could connect through client net. Until I checked network summary and noticed it had a different IP than actual config under interfaces and was now first IP of DHCP range.
The config was still showing the static IP I assigned it but FN decided to use DHCP anyway.

Reapplying settings made static IP work again.

I have not verified it again so it could be a fluke, although bugs kind of are.

Any one else had that happen or could verify it?
And should I open a bug report?

 

[pirateghost]

Are they both on the same subnet?

 

[no_connection]

Nope, edited to clarify a little bit more.

Simple dual NIC FN with two separate subnets. Both manually set.
Once we added the DHCP server to MGMT net to simplify handling for ourselves FN decided to ignore the statically assigned IP I had given it and ask for a DHCP assigned one instead.