Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1167096

Summary: installing 2 hypervisors from 2 rhel versions isn't allowed under the same cluster - error isn't visable to the user
Product: Red Hat Enterprise Virtualization Manager Reporter: Moran Goldboim <mgoldboi>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: ecohen, gklein, iheim, lpeer, lsurette, oourfali, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-25 07:56:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Moran Goldboim 2014-11-23 15:08:11 UTC 
Description of problem:
trying to install rhel6 hypervisor and rhel7 hypervisor will outcome with non-operational state for the second host.
-error isn't prompt to user, on event log, that the host is in this state due to that reason
-the only place it's mantioned is in engine.log [1]

Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.20.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
problem should be visible to the user, like it happens with problematic cpu- 
"Host my_host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all"

Expected results:


Additional info:
[1]2014-11-23 16:52:16,160 INFO  [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-40) [2ca5197c] Running command: SetNonOperationalVdsCommand internal: true. Entities affected 
:  ID: 16c1255d-1fb6-4c43-a809-f5eaef31064f Type: VDS
2014-11-23 16:52:16,161 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-40) [2ca5197c] START, SetVdsStatusVDSCommand(HostName = my_host, HostId = 16c1255d-1fb6-4c43-
a809-f5eaef31064f, status=NonOperational, nonOperationalReason=MIXING_RHEL_VERSIONS_IN_CLUSTER, stopSpmFailureLogged=false), log id: 358a0e1d
2014-11-23 16:52:16,172 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-40) [2ca5197c] FINISH, SetVdsStatusVDSCommand, log id: 358a0e1d
2014-11-23 16:52:16,197 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-40) [2ca5197c] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Mes
sage: Status of host my_host was set to NonOperational.
2014-11-23 16:52:16,233 INFO  [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-40) [7dc88c76] Running command: HandleVdsVersionCommand internal: true. Entities affected :  ID: 1
6c1255d-1fb6-4c43-a809-f5eaef31064f Type: VDS
2014-11-23 16:52:16,233 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-40) [7dc88c76] Host 16c1255d-1fb6-4c43-a809-f5eaef31064f : my_host is already in NonOperational
 status for reason MIXING_RHEL_VERSIONS_IN_CLUSTER. SetNonOperationalVds command is skipped.
Comment 1 Oved Ourfali 2014-11-25 07:56:36 UTC 

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