Red Hat Bugzilla – Bug 840888
[RHEVM] [backend] [Host Networking] DC/CL 3.0 cannot switch RHEVM network to another interface
Last modified: 2016-02-10 14:52:40 EST
Created attachment 598644 [details]
Description of problem:
In DC/CL 3.0 it is not possible to switch rhevm network from one host interface to another. Following error appears:
Previous network name is required.
Version-Release number of selected component (if applicable):
oVirt Engine Version: '3.1.0-6.el6ev'
Steps to Reproduce:
1. add host more than one NIC into 3.0 cluster
2. Hosts -> your host -> Network Interfaces -> rhevm interface -> Edit Management Network
3. Switch Interface: to different NIC click OK
Error message appears
Network should be switched
2012-07-17 15:43:22,503 WARN [org.ovirt.engine.core.bll.UpdateNetworkToVdsInterfaceCommand] (ajp-/0.0.0.0:8009-10) [241808ff] CanDoAction of action UpdateNetworkToVdsInterface failed. Reasons:NETWROK_OLD_NETWORK_NOT_SPECIFIED
This issue also appears when trying to bond rhevm interface with another.
Problem appears when trying to bond any two interfaces
In addition to comment 6, problem appears when trying to bond any 2 interface and one of them has already connected network.
The backend command checks if the network name on the nic (we want to switch rhevm to) is not null (or empty).
As the network name is null the canDoAction fails.
This is a wrong check cause the network name of the nic will always be null (or empty). If there was a network on the nic we won't be able to move the rhevm network to it.
A suggested patch: