Bug 1254336 - Network is un-managed when moving host to another cluster when the network exists on it
Summary: Network is un-managed when moving host to another cluster when the network ex...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 3.6.0
Assignee: Alona Kaplan
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 18:24 UTC by Meni Yakove
Modified: 2016-02-10 19:55 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-27 08:46:32 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
SN dialog (237.12 KB, image/png)
2015-08-17 18:25 UTC, Meni Yakove
no flags Details
engine, vdsm and supervdsm logs (289.95 KB, application/zip)
2015-08-17 18:30 UTC, Meni Yakove
no flags Details

Description Meni Yakove 2015-08-17 18:24:15 UTC
Description of problem:
When host have network attach to it ('net_1') and we move the host to another cluster that also have network 'net_1' the network become un-managed network in setupnetwork dialog but show as un-synced in the networks tab under the host

Version-Release number of selected component (if applicable):
rhevm-3.6.0-0.11.master.el6.noarch



Steps to Reproduce:
1. Create two DCs (dc1 and dc2)
2. Add to dc1 a host
3. Create net_1 on both DCs
4. Attach net_1 to host
5. Move the host from dc1 to dc1 

Actual results:
net_1 is un-managed

Expected results:
net_1 should be un-synced

Comment 1 Meni Yakove 2015-08-17 18:25:03 UTC
Created attachment 1064026 [details]
SN dialog

Comment 2 Meni Yakove 2015-08-17 18:30:08 UTC
Created attachment 1064039 [details]
engine, vdsm and supervdsm logs

Comment 3 Yaniv Lavi 2015-08-26 09:13:34 UTC
Is this resolved on latest build?

Comment 4 Meni Yakove 2015-08-27 08:46:32 UTC
work on the latest build.


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