Bug 1288116 - You can't change default cluster to a 3.x compat mode cluster.
Summary: You can't change default cluster to a 3.x compat mode cluster.
Keywords:
Status: CLOSED DUPLICATE of bug 1261851
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.2
: ---
Assignee: Eli Mesika
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 14:59 UTC by Bill Sanford
Modified: 2016-02-10 19:23 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 09:25:36 UTC
oVirt Team: Virt
Embargoed:
oourfali: ovirt-3.6.z?
rule-engine: planning_ack?
bsanford: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1288122 0 unspecified CLOSED version update for default cluster fails with NPE 2021-02-22 00:41:40 UTC

Internal Links: 1288122

Description Bill Sanford 2015-12-03 14:59:52 UTC
Description of problem:
When I start RHEV-M 3.6 for the first time, I want to have the "Default" Data Center and Cluster set to a 3.5 compat mode configuration.

I will edit the Data Center and change the "Compat Mode" to 3.5. I will then edit the Cluster to also show that it is also a 3.5 compat mode cluster.

I add a host and get an error after it is installed: "Host giediprime is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster Default which is set to version 3.6."

I then add a 3.5 Compat mode cluster to the default Data Center, switch the Host to Maintenance mode add it to the new 3.5 Compat mode Cluster, and the host comes up immediately.

Version-Release number of selected component (if applicable):
RHEV-M 3.6.0-22

How reproducible:
100%

Steps to Reproduce:
1. See above
2.
3.

Actual results:
The default Cluster is stuck in the 3.6 compat mode cluster.

Expected results:
The default Cluster can be changed to a 3.5 compat mode cluster to reflect the change in the "Default" Data Center.

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-12-03 15:48:23 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2015-12-03 15:48:23 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Einav Cohen 2015-12-04 05:41:19 UTC
I'm guessing that you cannot change the compatibility version of the default cluster due to bug 1288122 (NPE exception). so it's probably a duplicate.

Comment 4 Oved Ourfali 2015-12-07 12:27:24 UTC
Eli - can you take a look?

Comment 5 Eli Mesika 2015-12-07 15:24:35 UTC
Duplicate of 1261851

This should be resolved by back-porting https://gerrit.ovirt.org/#/c/48171/ on 3.6.z 

Oved, please decide which to close (this or 1261851)

Comment 6 Oved Ourfali 2015-12-08 09:25:36 UTC

*** This bug has been marked as a duplicate of bug 1261851 ***


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