Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 903107

Summary: Invalid package names in message dialog when starting virt-manager for the first time
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: virt-managerAssignee: virt-mgr-maint
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: berrange, crobinso, cwei, dallan, dyuan, hbrock, jbastian, jforbes, lcui, mjenner, mkletzan, mzhan, tzheng, virt-maint
Target Milestone: rc   
Target Release: 7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-manager-0.10.0-0.4.gitb68faac8.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:51:23 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: 883471    
Bug Blocks:    
Attachments:
Description Flags
screenshot of virt-manager none

Description tingting zheng 2013-01-23 08:15:58 UTC
Created attachment 685699 [details]
screenshot of virt-manager

Description of problem:
Package missing error shows when start virt-manager for the first time

Version-Release number of selected component (if applicable):
virt-manager-0.9.4-3.el7.noarch
libvirt-1.0.0-1.el7.x86_64
qemu-kvm-1.2.0-21.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Check all the packages installed:virt-manager,libvirt,qemu-kvm.

2.Start virt-manager for the first time or delete the existing qemu hypervisor connection then.
# virt-manager

3. Will get a package missing error:
The following packages are not installed:

::KVM_PACKAGES::

These are required to create KVM guests locally.
Would you like to install them now?

4.If choose no,it works well.

Actual results:
As steps

Expected results:
As qemu-kvm has installed and no package missing error showed.

Additional info:
Attached the screenshot.

Comment 2 Martin Kletzander 2013-02-06 16:26:45 UTC
This should be fixed in virt-manager-0.9.4-3.el7, could you try that and close this bug if it's true?  Thanks.

Comment 3 tingting zheng 2013-02-07 02:36:54 UTC
(In reply to comment #2)
> This should be fixed in virt-manager-0.9.4-3.el7, could you try that and
> close this bug if it's true?  Thanks.

I guess you mean virt-manager-0.9.4-4.el7 as the version mentioned in the bug is virt-manager-0.9.4-3.el7.

Tried with virt-manager-0.9.4-4.el7,Start virt-manager for the first time,will pop a window:
Packages required for KVM usage
The following packages are not installed:
qemu-system-x86
libvirt-daemon-qemu
These are required to create KVM guests locally.
Would you like to install them now?

If I choose "yes",it will try to install the packages,and fail with error:Error talking to PackageKit: org.freedesktop.PackageKit.Modify.NoPackagesFound: no package found

If I choose "no",it works well.

So,refer to the above steps,is it enough to close the bug?Thanks.

Comment 4 Martin Kletzander 2013-02-07 10:52:36 UTC
(In reply to comment #3)
Yes, I meant virt-manager-0.9.4-4.el7, sorry for that.  However this message is very unclear as these are invalid package names, so let's keep this bug open for that purpose.  I'll see what we can do, but it will probably have to wait after bigger changes take place (which will may solve this as well).

Comment 8 Dave Cantrell 2013-04-08 14:26:37 UTC
*** Bug 948458 has been marked as a duplicate of this bug. ***

Comment 9 Martin Kletzander 2013-06-03 12:43:08 UTC
Can you re-check how does this behave in your environment with the newest version?  Due to the switch to gtk3 and various other huge changes, it would be easiest to just check what's the status instead of hunting down the right commit.  Thanks

Comment 10 tingting zheng 2013-06-04 02:27:47 UTC
(In reply to Martin Kletzander from comment #9)
> Can you re-check how does this behave in your environment with the newest
> version?  Due to the switch to gtk3 and various other huge changes, it would
> be easiest to just check what's the status instead of hunting down the right
> commit.  Thanks

I tried latest virt-manager,the issue can not be reproduced.
virt-manager-0.10.0-0.4.gitb68faac8.el7.noarch
libvirt-1.0.5-2.el7.x86_64

Comment 11 tingting zheng 2013-06-04 10:10:42 UTC
Refer to comment 10,move the status of the bug as VERIFIED.

Comment 12 Ludek Smid 2014-06-13 12:51:23 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.