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:
$subject

Version-Release number of selected component (if applicable):
virt-manager-0.10.0-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Try connect to qemu+ssh://root@${hostname}/system
2. virt-manager suggests to install openssh-askpass
3. Hit 'no'.

Actual results:
virt-manager fails to connect

Expected results:
virt-manager succeeds to connect

Additional info:
this is a standard gnome3 install, with ssh-agent running and holding the keys needed to connect.  gnome asks for the passphrase when needed, which works just fine without openssh-askpass ...

If I'm not mistaken, the package in virt-manager is used for talking to the ssh not just because of the password request.  In case the remote is not in known hosts, I guess.  I'll see how we can make it easier for users.

not sure how this could be fixed without installing openssh-askpass (https://bugzilla.redhat.com/show_bug.cgi?id=754484).  Probably we could try to connect first and in case it fails we can repeat the operation asking the user to install openssh-askpass first.  What do you think?

We only ask 'do you want to install askpass' if ssh auth throws an error, and the error message mentions missing askpass binary, meaning ssh tried to launch it. We don't pre-emptively check for askpass or anything... So if ssh keys are properly setup, I don't think there should be any problem.

So closing as WORKSFORME, but if I'm wrong please reopen and provide full virt-manager --debug output when reproducing