Created attachment 704574[details]
Engine log
Description of problem:
When moving a host from a DC with a bridgeless network to another DC with a bridge network having the same name (both non-required), the host becomes non operational.
Version-Release number of selected component (if applicable):
rhevm-3.2.0-10.10.beta1.el6ev.noarch
How reproducible:
100%
Steps to Reproduce:
1. On the DC with the host create a new bridgeless (non-VM) network 'vnet1'.
2. Attach 'vnet1' network to an interface on the host using Setup Host Networks.
3. On the second DC create new bridge (VM) network 'vnet1'.
4. Move the host to the second DC.
Actual results:
Trying to activate the host doesn't work and the host becomes non operational with an error message in the events saying that the host doesn't comply with 'vnet1'. Only once 'vnet1' is synced (from Setup Host Networks) it is possible to activate the host.
Expected results:
The host should be operational after activating it (albeit with a warning about the unsynchronised network).
Additional info:
Having the networks (in both DC's) defined as non-required doesn't have an effect on the result.
The current behaviour fails the Host activation on purpose. Any VM running on this host will not be able to use the network since it is bridgeless, and this is a problematic condition that we prefer to block.
If it is desirable to change the current behaviour, we need to make changes in other flows to block the unwanted situation, for example upon running a VM, hot-plugging a nic, and rewiring a network on a VM nic.
This requires an RFE, since it is a change in behaviour which needs further consideration.
Following Muli's comments it's been agreed that this is not a bug and the TCMS case will be modified. There is a GUI issue that happens in this scenario but that will be opened in a separate bug.
Created attachment 704574 [details] Engine log Description of problem: When moving a host from a DC with a bridgeless network to another DC with a bridge network having the same name (both non-required), the host becomes non operational. Version-Release number of selected component (if applicable): rhevm-3.2.0-10.10.beta1.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. On the DC with the host create a new bridgeless (non-VM) network 'vnet1'. 2. Attach 'vnet1' network to an interface on the host using Setup Host Networks. 3. On the second DC create new bridge (VM) network 'vnet1'. 4. Move the host to the second DC. Actual results: Trying to activate the host doesn't work and the host becomes non operational with an error message in the events saying that the host doesn't comply with 'vnet1'. Only once 'vnet1' is synced (from Setup Host Networks) it is possible to activate the host. Expected results: The host should be operational after activating it (albeit with a warning about the unsynchronised network). Additional info: Having the networks (in both DC's) defined as non-required doesn't have an effect on the result.