Description of problem:
When applying a VM with multiple interfaces with the same name, the VM is rejected but kubemacpool is mishandling the MACs, causing a side effect where that MAC is no longer usable (it is "taken" by the ghost VM).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. deploy kubemacpool
2. apply a VM with multiple duplicate interface names. For example
3. try to apply a new VM with the MACs given to the rejected VM.

Actual results:

Expected results:

Additional info: