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

Bug 1218581

Summary: [HC] vdsm checks for qemu-kvm-rhev missing qemu-kvm-ev
Product: [Retired] oVirt Reporter: Sandro Bonazzola <sbonazzo>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: Nikolai Sednev <nsednev>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.6CC: bazulay, bugs, ecohen, gklein, istein, lsurette, mgoldboi, rbalakri, ybronhei, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: ovirt-3.6.0-alpha1.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1219754 (view as bug list) Environment:
Last Closed: 2015-11-04 12:57:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1219754    

Description Sandro Bonazzola 2015-05-05 09:56:16 UTC
In VDSM logs I see:

Thread-95::DEBUG::2015-05-05 11:53:00,824::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,825::caps::757::root::(_getKeyPackages) rpm package ('qemu-kvm', 'qemu-kvm-rhev') not found
Thread-95::DEBUG::2015-05-05 11:53:00,825::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-object',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,825::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-plugin',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,826::caps::757::root::(_getKeyPackages) rpm package ('qemu-img', 'qemu-img-rhev') not found
Thread-95::DEBUG::2015-05-05 11:53:00,826::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-account',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,826::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-proxy',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,826::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-doc',) not found
Thread-95::DEBUG::2015-05-05 11:53:00,826::caps::757::root::(_getKeyPackages) rpm package ('gluster-swift-container',) not found

please change the above code for including qemu-kvm-ev:

# rpm -qa |grep qemu|sort
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64
qemu-img-ev-2.1.2-23.el7.1.x86_64
qemu-kvm-common-ev-2.1.2-23.el7.1.x86_64
qemu-kvm-ev-2.1.2-23.el7.1.x86_64
qemu-kvm-tools-ev-2.1.2-23.el7.1.x86_64

Comment 1 Nikolai Sednev 2015-05-31 13:57:15 UTC
Works for me on these components at host side, I didn't deployed HC, but regular HE, qemu-kvm-ev-2.1.2-23.el7_1.3.1.x86_64 is already there:

# rpm -qa vdsm libvirt* sanlock* qemu-kvm* ovirt* mom
libvirt-daemon-driver-interface-1.2.8-16.el7_1.3.x86_64
vdsm-4.17.0-822.git9b11a18.el7.noarch
sanlock-python-3.2.2-2.el7.x86_64
qemu-kvm-common-ev-2.1.2-23.el7_1.3.1.x86_64
libvirt-python-1.2.8-7.el7_1.1.x86_64
libvirt-daemon-kvm-1.2.8-16.el7_1.3.x86_64
ovirt-release-master-001-0.8.master.noarch
ovirt-engine-sdk-python-3.6.0.0-0.13.20150515.gitdd15fbf.el7.centos.noarch
libvirt-client-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-storage-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-network-1.2.8-16.el7_1.3.x86_64
sanlock-lib-3.2.2-2.el7.x86_64
qemu-kvm-ev-2.1.2-23.el7_1.3.1.x86_64
libvirt-daemon-1.2.8-16.el7_1.3.x86_64
libvirt-lock-sanlock-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-secret-1.2.8-16.el7_1.3.x86_64
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.3.x86_64
ovirt-hosted-engine-setup-1.3.0-0.0.master.20150518075146.gitdd9741f.el7.noarch
libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.3.x86_64
mom-0.4.4-0.0.master.20150515133332.git2d32797.el7.noarch
qemu-kvm-tools-ev-2.1.2-23.el7_1.3.1.x86_64
ovirt-host-deploy-1.4.0-0.0.master.20150505205623.giteabc23b.el7.noarch
libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.3.x86_64
ovirt-hosted-engine-ha-1.3.0-0.0.master.20150424113553.20150424113551.git7c14f4c.el7.noarch
sanlock-3.2.2-2.el7.x86_64

Components installed on engine:
ovirt-engine-cli-3.6.0.0-0.2.20150518.gite3609e3.el6.noarch
ovirt-engine-setup-base-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-host-deploy-java-1.4.0-0.0.master.20150515080139.giteabc23b.el6.noarch
ovirt-engine-userportal-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-sdk-python-3.6.0.0-0.13.20150515.gitdd15fbf.el6.noarch
ovirt-iso-uploader-3.6.0-0.0.master.20150410142241.git1a680f9.el6.noarch
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-tools-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-backend-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-setup-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-release-master-001-0.8.master.noarch
ovirt-host-deploy-1.4.0-0.0.master.20150515080139.giteabc23b.el6.noarch
ovirt-image-uploader-3.6.0-0.0.master.20150128151752.git3f60704.el6.noarch
ovirt-engine-lib-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-jboss-as-7.1.1-1.el6.x86_64
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-restapi-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-dbscripts-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-engine-3.6.0-0.0.master.20150519172219.git9a2e2b3.el6.noarch
ovirt-guest-agent-1.0.10.2-1.el6.noarch

Comment 2 Sandro Bonazzola 2015-11-04 12:57:33 UTC
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.