Bug 1401888 - "Save this password in your keyring" checkbox is disabled when ssh to host
Summary: "Save this password in your keyring" checkbox is disabled when ssh to host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.9
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 10:56 UTC by zhoujunqin
Modified: 2016-12-21 03:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 17:21:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description zhoujunqin 2016-12-06 10:56:54 UTC
Description of problem:
When using ssh to a rhel6.9 host, then open a guest with password setting, finding "Save this password in your keyring" checkbox is diabled.

Version-Release number of selected component (if applicable):
libvirt-0.10.2-62.el6.x86_64
virt-manager-0.9.0-33.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
 On local machineA
1. Open virt-manager, make sure a good guest is in shutdown status.	
2. Open guest details page, Click Display Spice in hardware tab, add
a password to "aabb", Apply.	

Then on machineB, using ssh -X to connect to machineA.
# ssh root@machineA  -X
3. Launch virt-manager.
# virt-manager
4. Start the guest, when the guest boot up, An password need input to open console.

Actual results:
"Save this password in your keyring" checkbox is diabled

Expected results:
"Save this password in your keyring" checkbox is enabled.

Additional info:

Comment 3 Pavel Hrdina 2016-12-20 17:21:14 UTC
That feature depends on availability and usability of gnome-keyring.  In case of RHEL-6 the gnome-keyring is not available if you are connected over ssh.  There is nothing that can be done on virt-manager side and it's not a bug in virt-manager.


Note You need to log in before you can comment on or make changes to this bug.