Bug 1290314
Summary: | Unexpected "=" display before some words in --cdrom part | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Xiaodai Wang <xiaodwan> |
Component: | virt-manager | Assignee: | Pavel Hrdina <phrdina> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | juzhou, mxie, mzhan, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-manager-1.3.2-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 02:00:41 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: | |
Embargoed: |
Description
Xiaodai Wang
2015-12-10 08:31:50 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions I can reproduce this bug with package: virt-manager-1.2.1-8.el7.noarch virt-install-1.2.1-8.el7.noarch Steps are the same as description above. Then try to verify with new build: virt-manager-1.4.0-1.el7.noarch virt-install-1.4.0-1.el7.noarch Steps: 1. Run "man virt-install", check below example. Results: 1. #man virt-install --cdrom OPTIONS File or device used as a virtual CD-ROM device. It can be path to an ISO image or a URL from which to fetch/access a minimal boot ISO image. The URLs take the same format as described for the "--location" argument. If a cdrom has been specified via the "--disk" option, and neither "--cdrom" nor any other install option is specified, the "--disk" cdrom is used as the install media. According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED. 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. https://rhn.redhat.com/errata/RHBA-2016-2269.html |