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 1213202 - [virt-manager]wrong error message always show after add the second one failed for a single supported device
Summary: [virt-manager]wrong error message always show after add the second one failed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1183604 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-20 02:51 UTC by vivian zhang
Modified: 2015-11-19 05:25 UTC (History)
4 users (show)

Fixed In Version: virt-manager-1.2.0-1-el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 05:25:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-manager debug log (19.96 KB, text/plain)
2015-04-20 02:51 UTC, vivian zhang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2206 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2015-11-19 08:17:29 UTC

Description vivian zhang 2015-04-20 02:51:02 UTC 
Created attachment 1016198 [details]
virt-manager debug log

Description:
For watchdog, tpm and panic devices, libvirt only support add single one for them. After trying to add the second one for them, the wrong error message will always show even though you do other right actions with virt-manager.

Version-Release number of selected component (if applicable):
virt-manager-1.1.0-12.el7.noarch
qemu-kvm-rhev-2.2.0-8.el7.x86_64
libvirt-1.2.14-1.el7.x86_64



How reproducible:
100%

Steps:

1. launch virt-manager
2. prepare a health guest without tpm watchdog or panic devices
3. Open the guest and turn to "Hardware Details" page, and then click "Add Hardware"->choose "watchdog"-> add the first one watchdog device -> click 'Finish'.It will success to be added to guest.
4. try to add the second one, virt-manager report error
"Error adding device: internal error: only a single watchdog device is supported"
5. try to add other devices with virt-manager, such as video device, the above error "Error adding device: internal error: only a single watchdog device is supported" show again, you can not do any other right actions for this guest with virt-manager.
6. the same result also hit on tpm and panic devices




Actual result:
After step 4, the error message always show again and again for other actions in virt-manager

Expect result:
After step 4,the wrong message should not show up even though you do other right actions for guest

Additional info:
virt-manager debug info will be attached
Comment 3 Giuseppe Scrivano 2015-04-20 12:42:04 UTC 
fixed upstream by:

commit 1c63c2b0d9029b794793ebaa456bf2b139b5d77c
Author: Cole Robinson <crobinso>
Date:   Thu Apr 9 13:01:38 2015 -0400

    libvirtobject: Invalidate cache if redefine fails
Comment 5 Giuseppe Scrivano 2015-05-06 08:36:50 UTC 
*** Bug 1183604 has been marked as a duplicate of this bug. ***
Comment 6 fwu 2015-05-18 04:59:46 UTC 
I can reproduce this issue with package:
virt-manager-1.1.0-12.el7.noarch

Steps are same as those in description.

Result:
The error message come out as described.
The problem also exists for TPM and panic notifier.

Then try to verify with new build:
virt-manager-1.2.0-3.el7.noarch

Steps:

1. launch virt-manager
2. prepare a health guest without tpm watchdog or panic devices
3. Open the guest and turn to "Hardware Details" page, and then click "Add Hardware">choose "watchdog"> add the first watchdog device -> click 'Finish'. The watchdog device will be added to the guest successfully.
4. Try to add the second one, virt-manager report error
"Error adding device: internal error: only a single watchdog device is supported".
5. Try to add other devices with virt-manager, such as video device, sound device etc.

Result:
After first watchdog device/TPM/panic notifier was added, error message will occur when adding the same device second time.
Other devices such as video device can be added successfully.

According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED.
Comment 9 errata-xmlrpc 2015-11-19 05:25:31 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
Note You need to log in before you can comment on or make changes to this bug.