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.
Description of problem:
Set a spice password for a guest, if input a wrong passwd
when open the guest with virt-manager, no error message
comes out and the console will be black.
Version-Release number of selected component (if applicable):
virt-manager-1.1.0-4.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install a spice guest and set the spice password : "aabb"
# virt-manager
Click "Details-> Display spice -> Check on option Password -> input password : aabb -> Click Apply"
2. # virt-manager, click "run" and open the guest
double click on the guest to open it, input a wrong passwd like "ccdd"
in the input dialog
3. click "Login"
Actual results:
After step 3, the console will be black, and no error message to
tell the password is wrong or go back to input password again.
Expected results:
There should come out a message to tell user the password is wrong or
go back to input again.
Additional info:
Comment 2Giuseppe Scrivano
2014-10-15 13:27:09 UTC
I've investigated it on Fedora 20 where I could reproduce the same issue and it looks like a problem in the python bindings of spice-gtk, that does not report a SpiceClientGLib.ChannelEvent.ERROR_AUTH event when the password is not correct.
I've compared the code to virt-viewer (it works correctly), which is doing the same thing as virt-manager using the C version of spice-gtk.
Comment 3Christophe Fergeau
2014-10-21 12:06:17 UTC
The problem is that the main channel gets recreated after an ERR_AUTH, and virt-manager is not reconnecting to the channel-event signal on this new main channel.
diff --git a/virtManager/console.py b/virtManager/console.py
index 67bfe10..dc2f813 100644
--- a/virtManager/console.py
+++ b/virtManager/console.py
@@ -405,6 +406,7 @@ class SpiceViewer(Viewer):
self.console.disconnected()
elif event == SpiceClientGLib.ChannelEvent.ERROR_AUTH:
self.console.activate_auth_page()
+ self.main_channel = None
elif event in [SpiceClientGLib.ChannelEvent.ERROR_CONNECT,
SpiceClientGLib.ChannelEvent.ERROR_IO,
SpiceClientGLib.ChannelEvent.ERROR_LINK,
avoids the issue on my Fedora 21
I can reproduce this issue with package:
virt-manager-1.1.0-4.el7.noarch
then try to verify with new build:
virt-manager-1.1.0-5.el7.noarch
Steps:
1. Install a spice guest and set the spice password : "aabb"
# virt-manager
Click "Details-> Display spice -> Check on option Password -> input password : aabb -> Click Apply"
2. # virt-manager, click "run" and open the guest
double click on the guest to open it, input a wrong passwd like "ccdd"
in the input dialogue.
3. click "Login"
Result: After step3 with wrong password, we cannot login the guest, and display going back to input password again.
So move this bug from ON_QA to VERIFIED.
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-0427.html