| Summary: | [RHEL 6.1] "virt-manager -h" command from ssh session gives error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | asilva <asilva> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | dyuan, hjiang, jmunilla, jwilleford, mliu, mzhan, rdassen |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No description necessary
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 16:07:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 688244 | ||
|
Description
asilva
2011-03-22 17:07:29 UTC
Thanks, fixed upstream: http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=ee3e0ba45004859f95eb8a54166bc4aad969b605 Tagging as a regression. Fix is simple and low risk. Fixed in virt-manager-0.9.0-2.el6 verified with the following components: virt-manager-0.9.0-5.el6.x86_64 libvirt-0.9.4-0rc1.2.el6.x86_64 Steps: 1. # ssh 10.66.3.130 root.3.130's password: Last login: Wed Aug 3 21:14:29 2011 from 10.66.15.50 2. # virt-manager -h Usage: virt-manager [options] ... 3. # ssh 10.66.3.130 -X root.3.130's password: Last login: Wed Aug 3 23:08:54 2011 from 10.66.3.131 4. # virt-manager -h Usage: virt-manager [options] ...
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No description necessary
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. http://rhn.redhat.com/errata/RHBA-2011-1642.html |