Bug 1294498 - [RFE] Engine should warn admin about incompatible hypervisor version when changing DC/Cluster compatibility mode
Summary: [RFE] Engine should warn admin about incompatible hypervisor version when cha...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-28 14:07 UTC by Igor Netkachev
Modified: 2023-09-14 03:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-08 12:35:23 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Igor Netkachev 2015-12-28 14:07:25 UTC
Description of problem:

Today I've got a case from customer who was using RHEV-M 3.4 and RHEL/RHEV 6.5 hypervisors , after upgrading Manager to 3.5 and changing compatibility mode to 3.5 for both Datacenter and Cluster customer was unable to activate the hypervisors anymore until he upgraded them too as per https://access.redhat.com/solutions/463903

Shouldn't RHEV Manager warn the customer at the stage where he's trying to change compatibility mode that Datacenter/Cluster contains hypervisor which are not compatible with the mode being set? This would help to prevent the issues like in the case that I had.

Please let me know if that's possible and makes any sense in your opinion.


--
Kind Regards,
Igor Netkachev
Technical Support Engineer
Red Hat Global Support Services

Comment 2 Oved Ourfali 2016-01-10 13:09:42 UTC
Before allowing you to change a cluster level, we do check that all hosts are compatible with this cluster level. What was the exact versions of engine+VDSM the customer worked with?
In case of node, what was the image version?

Comment 3 Red Hat Bugzilla 2023-09-14 03:15:29 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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