Description of problem: The existing behaviour for link/unlink state for external network is as follow: You get Can do action if you try to unlink NIC with external network. But if you unplug that NIC and try to plug it back when it is unlinked an action succeeds. So you find a way to get plugged and unlinked NIC with external network when you are supposed to get Can do action Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create VM with external network 2. Unlink and unplug it 3. Plug it back Actual results: An action succeeds and you have plugged and unlinked NIC with external network on VM Expected results: An action should fail with Can do action Additional info:
This behavior is inconsistent and misleading, but should not block rhev-3.4.0
This could be solved on both backend and frontend, I think that blocking this in the backend should be enough.
fixed in vt3, moving to on_qa. if you believe this bug isn't released in vt3, please report to rhev-integ
VERIFIED Red Hat Enterprise Virtualization Manager Version: 3.5.0-0.12.beta.el6ev Error while executing action: rhel6.6: Cannot edit Interface. Plugged and unlinked VM network interface with external network is not supported.
rhev 3.5.0 was released. closing.