Bug 1279955

Summary:	Clusters with no management network after upgrade
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yevgeny Zaspitsky <yzaspits>
Component:	ovirt-engine	Assignee:	Yevgeny Zaspitsky <yzaspits>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	danken, eedri, gklein, jbelka, jentrena, lsurette, masayag, mburman, myakove, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi, yzaspits
Target Milestone:	ovirt-3.6.1	Flags:	ylavi: Triaged+
Target Release:	3.6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1372955 (view as bug list)		Environment:
Last Closed:	2016-04-20 01:33:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1283458, 1285700, 1372955

Description Yevgeny Zaspitsky 2015-11-10 15:13:32 UTC

Description of problem:
Clusters with no management network after upgrade

Version-Release number of selected component (if applicable):
rhev-m 3.6.0-3

How reproducible:
100%

Steps to Reproduce:
1. In v3.5 create a cluster with a host in it
2. Upgrade to 3.6
3.

Actual results:
The cluster appears with no management network

Expected results:
rhevm network should be the management network

Additional info:
Other side effects:
1. Setup networks dialog keep loading endlessly
2. In create new VM dialog vNIC profile list is empty

Comment 1 Eyal Edri 2015-11-10 19:07:00 UTC

since we target beta2 build to support upgrades, this is a blocker.
proposing flag.

Comment 3 Michael Burman 2015-11-24 14:30:33 UTC

Hi Yevgeny,

Just finished upgrade from rhevm-3.5.6.2-0.1.el6ev.noarch to rhevm-3.6.0.3-0.1.el6.noarch
And i just want to be sure is this BZ^^ going to fix all the next issues or additional bugs required:

- No management network for clusters after upgrade
- Setup Networks dialog keep loading forever
- vNIC profile list is empty for new vNICs for existing VMs, exist ones and for new VMs.
- The default management network for new 3.6 DCs and clusters is 'rhevm'.

Thanks,

Comment 4 Yevgeny Zaspitsky 2015-11-25 07:58:04 UTC

(In reply to Michael Burman from comment #3)
> Hi Yevgeny,
> 
> Just finished upgrade from rhevm-3.5.6.2-0.1.el6ev.noarch to
> rhevm-3.6.0.3-0.1.el6.noarch
> And i just want to be sure is this BZ^^ going to fix all the next issues or
> additional bugs required:
> 
> - No management network for clusters after upgrade
> - Setup Networks dialog keep loading forever
> - vNIC profile list is empty for new vNICs for existing VMs, exist ones and
> for new VMs.
Yes, those would be fixed.

> - The default management network for new 3.6 DCs and clusters is 'rhevm'.
The default management network will continue being 'rhevm' for an existing installation and 'ovirtmgmt' for a new installation (as designed).
> 
> Thanks,

Comment 5 Michael Burman 2015-11-25 08:26:21 UTC

What do you mean by new installation?

To be more clear -->
After upgrade from 3.5.z to 3.6.0, when creating new 3.6 DC/Cluster in the upgraded engine, i get as default 'rhevm' and not 'ovirtmgmt' network.
It is a bug, the question is, if it will be fixed as part of this one^^ and are you aware of this bug?
Thanks,

Comment 6 Yevgeny Zaspitsky 2015-11-25 11:12:01 UTC

AFAIK that isn't a bug, but a desired behavior.
Anyhow that is not related to this bug nor to mgmt network per cluster feature.

Comment 7 Jiri Belka 2015-11-26 09:53:30 UTC

works for me with 3.6.1-0.2.el6.noarch, see https://bugzilla.redhat.com/show_bug.cgi?id=1285309#c3

Comment 8 Michael Burman 2015-11-26 10:08:28 UTC

Verified on - 3.6.1-0.2.el6

Comment 9 Dan Kenigsberg 2015-12-10 14:56:58 UTC

*** Bug 1284584 has been marked as a duplicate of this bug. ***