Bug 617391 - 'connection' dropdown is very confusing if you have remote hypervisor access via ssh key
Summary: 'connection' dropdown is very confusing if you have remote hypervisor access ...
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Keywords: RHELNAK
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-22 22:02 UTC by Máirín Duffy
Modified: 2011-05-19 13:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-05-19 13:46:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot of the dropdown in question (22.31 KB, image/png)
2010-07-22 22:02 UTC, Máirín Duffy
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0637 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2011-05-18 17:55:47 UTC

Description Máirín Duffy 2010-07-22 22:02:14 UTC
Created attachment 433819 [details]
screenshot of the dropdown in question

Description of problem:
i'm not a super-technical user but i can usually hold my own.

i needed to connect to a remote hypervisor for which i only have access to the root account via ssh key. 

look at the attached screenshot of the 'connection' dropdoown of the 'add connection' dialog. which option would you have picked in the dropdown? i certainly wasn't sure.

(in the end, ssh tunnel was the option that worked, which wasn't very intuitive to me)

Version-Release number of selected component (if applicable):
virt-manager-0.8.4-7.el6.noarch

Comment 2 RHEL Product and Program Management 2010-07-22 22:37:41 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Cole Robinson 2010-08-24 19:51:15 UTC
Yeah, that dialog hasn't seen a lot of love over the years and is pretty ugly. There have been numerous complaints about the lack of $USER transparency.

I've reworked this dialog upstream:

http://fedorapeople.org/~crobinso/tmp/vmm-addconn1.png
http://fedorapeople.org/~crobinso/tmp/vmm-addconn2.png

Hopefully it should solve some of the issues you were hitting. Feedback appreciated.

Comment 4 Ray Strode [halfline] 2010-08-24 20:10:53 UTC
Hi Cole,

That reworking of the UI looks much better than the one I posted a screesnhot of!! Thanks :)

Comment 5 Máirín Duffy 2010-08-24 20:16:13 UTC
Whoops sorry, that was me. Ray borrowed my laptop when his laptop's backlight broke.

Comment 6 Cole Robinson 2011-01-14 22:21:11 UTC
Fixed in virt-manager-0.8.6-1.el6

Comment 8 zhanghaiyan 2011-03-02 05:49:35 UTC
Verified this bug with virt-manager-0.8.6-2.el6.noarch

The dialog looks the same with in comments

Comment 9 errata-xmlrpc 2011-05-19 13:46:28 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0637.html


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