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
since we target beta2 build to support upgrades, this is a blocker. proposing flag.
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,
(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,
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,
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.
works for me with 3.6.1-0.2.el6.noarch, see https://bugzilla.redhat.com/show_bug.cgi?id=1285309#c3
Verified on - 3.6.1-0.2.el6
*** Bug 1284584 has been marked as a duplicate of this bug. ***