Bug 840888 - [RHEVM] [backend] [Host Networking] DC/CL 3.0 cannot switch RHEVM network to another interface
Summary: [RHEVM] [backend] [Host Networking] DC/CL 3.0 cannot switch RHEVM network to ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Moti Asayag
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-17 13:59 UTC by Martin Pavlik
Modified: 2016-02-10 19:52 UTC (History)
10 users (show)

Fixed In Version: si14
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 849971 (view as bug list)
Environment:
Last Closed: 2012-07-18 06:43:19 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot 1 (210.59 KB, image/png)
2012-07-17 13:59 UTC, Martin Pavlik
no flags Details

Description Martin Pavlik 2012-07-17 13:59:12 UTC
Created attachment 598644 [details]
screenshot 1

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:

Error:

localhost.localdomain:

    Previous network name is required.


Version-Release number of selected component (if applicable):
oVirt Engine Version: '3.1.0-6.el6ev' 

How reproducible:
always

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
  
Actual results:
Error message appears

Expected results:
Network should be switched

Additional info:

engine.log
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

Comment 1 Martin Pavlik 2012-07-17 14:28:04 UTC
This issue also appears when trying to bond rhevm interface with another.

Comment 6 Martin Pavlik 2012-07-26 14:27:45 UTC
Problem appears when trying to bond any two interfaces

Comment 7 Martin Pavlik 2012-07-26 14:53:59 UTC
In addition to comment 6, problem appears when trying to bond any 2 interface and one of them has already connected network.

Comment 8 Martin Pavlik 2012-07-26 14:54:14 UTC
In addition to comment 6, problem appears when trying to bond any 2 interface and one of them has already connected network.

Comment 11 Alona Kaplan 2012-07-30 14:49:54 UTC
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.

Comment 12 Moti Asayag 2012-08-07 10:42:49 UTC
A suggested patch:

http://gerrit.ovirt.org/#/c/6971


Note You need to log in before you can comment on or make changes to this bug.