Bug 1046651

Summary: should add "qemu-kvm-rhev" package to acceptance list when first connect to a qemu hypervisor
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: virt-managerAssignee: Pavel Hrdina <phrdina>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: cwei, dyuan, juzhang, mjenner, mkletzan, mzhan, rbalakri, tzheng, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-manager-1.2.1-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 889428 Environment:
Last Closed: 2015-11-19 05:22:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 889428    
Bug Blocks:    
Attachments:
Description Flags
virt-manager_1
none
virt-manager_2 none

Comment 3 Cui Lei 2014-03-05 02:59:13 UTC 
Add one issue scenario:
qemu-kvm-rhev-1.5.3-50.el7.x86_64
libvirt-1.1.1-25.el7.x86_64
virt-manager-0.10.0-18.el7.noarch

When first connect to q qemu hypervisor, after click "Yes" when hint qemu-kvm are not installed, a warning window would popup "Failed to install software, All of the packages selected for install are already installed on the system". It is obviously conflict with former warning window.

Detail please refer to attachment
Comment 4 Cui Lei 2014-03-05 03:00:12 UTC 
Created attachment 870739 [details]
virt-manager_1
Comment 5 Cui Lei 2014-03-05 03:01:38 UTC 
Created attachment 870740 [details]
virt-manager_2
Comment 7 Giuseppe Scrivano 2014-10-31 14:00:00 UTC 
I agree with Martin and I think that on RHEV (maybe RHEL as well), instead of having some extra logic, virt-manager should not suggest installing any package, as it is out of its scope.

Anyone against that?
Comment 9 Pavel Hrdina 2015-06-17 16:04:05 UTC 
Upstream commit proposed:

https://www.redhat.com/archives/virt-tools-list/2015-June/msg00181.html
Comment 10 Pavel Hrdina 2015-06-22 13:03:36 UTC 
Upstream commit:

commit cbd7e33a09ee59a9d319337af63fcdbbe063e3c0
Author: Pavel Hrdina <phrdina>
Date:   Wed Jun 17 18:03:15 2015 +0200

    spec: we don't need to depend on qemu-kvm
    
    Similarly as in commit 95cda553, just remove the dependency on qemu-kvm
    package for RHEL builds.  We don't need it, becase libvirt-daemon-kvm
    will handle this dependency correctly for us even in case that only
    qemu-kvm-rhev is present.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1046651
    
    Signed-off-by: Pavel Hrdina <phrdina>
Comment 13 Xiaodai Wang 2015-06-26 08:10:09 UTC 
I can reproduce this bug with package:
# rpm -q virt-manager
virt-manager-1.1.0-13.el7.noarch
qemu-kvm-rhev-2.3.0-2.el7.x86_64

Steps:
1. Launch virt-manager for the first time or delete the existing qemu hypervisor connection then.
# virt-manager

Result:
A message box pops up.

Python requires additional software
Additional software is required
qemu-kvm
Do you want to search for and install this software now?


Then try to verify with latest build:
virt-manager-1.2.1-2.el7.noarch.rpm  


Result:
No message box pops up and can connect to default connection successfully.

Additional info:
if no qemu-kvm is installed, An error will report. I think it's correct.

Unable to connect to libvirt.
Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory


According to the result above in the latest version of virt-manager, this bug is fixed. and move it to verified.
Comment 15 errata-xmlrpc 2015-11-19 05:22:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2206.html