Description of problem: The VNIC profile for specific network should be unique, but if you update non-VM network to be VM and in the same step add it several VNIC profile with the same name then the action succeeds Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create non-VM network 2. Update it to be VM network and add it several VNIC profiles with the same name in that step 3. Actual results: Network will become VM and will have several VNIC profiles with the same name Expected results: Network should have only one profile with specific name (should be unique) Additional info:
Works in is27 Error while executing action: Cannot add VM network interface profile. The VM network interface profile's name is already used by an existing profile for the same network. -Please choose a different name. only one profile with unique name is added
Closing - RHEV 3.3 Released