Bug 1401888

Summary: "Save this password in your keyring" checkbox is disabled when ssh to host
Product: Red Hat Enterprise Linux 6 Reporter: zhoujunqin <juzhou>
Component: virt-managerAssignee: Pavel Hrdina <phrdina>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9CC: kuwei, mxie, rbalakri, tzheng, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 17:21:14 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:

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.