Bug 1007337 - RHEL6.4 host in 3.3 cluster became 'Non Operational' state because supported_emulated_machines does not report rhel6.5.0
Summary: RHEL6.4 host in 3.3 cluster became 'Non Operational' state because supported_...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 09:50 UTC by Jiri Belka
Modified: 2013-09-12 10:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-12 10:46:29 UTC
oVirt Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Jiri Belka 2013-09-12 09:50:58 UTC
Description of problem:
Between is13 and is14 there's was a change in DB in ClusterEmulatedMachines which added rhel6.5.0. qemu-kvm-rhev from RHEL6.4 does not report this emulated machines thus the host previously running find is not in Non operational state.

2013-Sep-12, 11:35
	
Host dell-r210ii-04 does not comply with the cluster Default emulated machines. The Hosts emulated machines are rhel6.4.0,pc,rhel6.3.0,rhel6.2.0,rhel6.1.0,rhel6.0.0,rhel5.5.0,rhel5.4.4,rhel5.4.0 and the cluster is rhel6.5.0}

rhel6.4:

# /usr/libexec/qemu-kvm -M ?
Supported machines are:
pc         RHEL 6.4.0 PC (alias of rhel6.4.0)
rhel6.4.0  RHEL 6.4.0 PC (default)
rhel6.3.0  RHEL 6.3.0 PC
rhel6.2.0  RHEL 6.2.0 PC
rhel6.1.0  RHEL 6.1.0 PC
rhel6.0.0  RHEL 6.0.0 PC
rhel5.5.0  RHEL 5.5.0 PC
rhel5.4.4  RHEL 5.4.4 PC
rhel5.4.0  RHEL 5.4.0 PC
[root@dell-r210ii-04 ~]# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.355.el6_4.3.x86_64

select vds_id,supported_emulated_machines from vds_dynamic ;                                                                                          
                vds_id                |                                 supported_emulated_machines                                  
--------------------------------------+----------------------------------------------------------------------------------------------
 77f5c975-01d2-46ad-bb75-1e6f774608a2 | rhel6.5.0,pc,rhel6.4.0,rhel6.3.0,rhel6.2.0,rhel6.1.0,rhel6.0.0,rhel5.5.0,rhel5.4.4,rhel5.4.0
 978ec6fc-10d1-43ca-9980-5c68859521b4 | rhel6.4.0,pc,rhel6.3.0,rhel6.2.0,rhel6.1.0,rhel6.0.0,rhel5.5.0,rhel5.4.4,rhel5.4.0

rhel6.5:

# /usr/libexec/qemu-kvm -M ? ; rpm -q qemu-kvm-rhev
Supported machines are:
pc         RHEL 6.5.0 PC (alias of rhel6.5.0)
rhel6.5.0  RHEL 6.5.0 PC (default)
rhel6.4.0  RHEL 6.4.0 PC
rhel6.3.0  RHEL 6.3.0 PC
rhel6.2.0  RHEL 6.2.0 PC
rhel6.1.0  RHEL 6.1.0 PC
rhel6.0.0  RHEL 6.0.0 PC
rhel5.5.0  RHEL 5.5.0 PC
rhel5.4.4  RHEL 5.4.4 PC
rhel5.4.0  RHEL 5.4.0 PC
qemu-kvm-rhev-0.12.1.2-2.401.el6.x86_64

Version-Release number of selected component (if applicable):
is14

How reproducible:
100%

Steps to Reproduce:
1. is13 + have a 3.3 cluster
2. have rhel 6.4 in cluster
3. upgrade to is14

Actual results:
rhel6.4 host in 3.3 cluster became non-operational

Expected results:
3.3 cluster should have working rhel6.4 hosts

Additional info:

Comment 1 Jiri Belka 2013-09-12 09:55:34 UTC
comparison with older is (though is13):

41 | ClusterEmulatedMachines | rhel6.4.0,pc-1.0 | 3.3

Comment 3 Itamar Heim 2013-09-12 10:46:29 UTC
actually, we removed the support for 6.4 which was temporary until 6.5 was viable.
6.4 is not supported in a 3.3 cluster


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