Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionhyao@redhat.com
2013-10-29 01:46:09 UTC
Description
Typo in virt-install manual on RHEL6, should use "an"instead of "and" in format option description.
Version:
# rpm -qa python-virtinst libvirt
python-virtinst-0.600.0-18.el6.noarch
libvirt-0.10.2-29.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.
#man virt-install
format
...
With libvirt 0.8.3 and later, this option should be specified if reusing and existing disk image, since libvirt
does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2
image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image.
2. Check the virt-install manual on rhel7
# rpm -qa libvirt virt-manager
libvirt-1.1.1-10.el7.x86_64
virt-manager-0.10.0-4.el7.noarch
#man virt-install
format
...
With libvirt 0.8.3 and later, this option should be specified if reusing an existing disk image, since libvirt does not
autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want
to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image.
Actual results:
Typo of "reusing and existing disk image" is listed in virt-install manual on RHEL6, not on RHEL7.
Expected results:
List "reusing an existing disk image" in virt-install manual on RHEL6.
Additional info:
Reproduce with python-virtinst-0.600.0-18.el6.noarch.
Verified with package:
python-virtinst-0.600.0-20.el6.noarch
steps:
# man virt-install
format
...
With libvirt 0.8.3 and later, this option should be specified if reusing an existing disk image, since
libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing
an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be
able to read your disk image.
No typo of "reusing and existing disk image" showed,so move 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.
http://rhn.redhat.com/errata/RHBA-2014-1444.html
Description Typo in virt-install manual on RHEL6, should use "an"instead of "and" in format option description. Version: # rpm -qa python-virtinst libvirt python-virtinst-0.600.0-18.el6.noarch libvirt-0.10.2-29.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. #man virt-install format ... With libvirt 0.8.3 and later, this option should be specified if reusing and existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image. 2. Check the virt-install manual on rhel7 # rpm -qa libvirt virt-manager libvirt-1.1.1-10.el7.x86_64 virt-manager-0.10.0-4.el7.noarch #man virt-install format ... With libvirt 0.8.3 and later, this option should be specified if reusing an existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image. Actual results: Typo of "reusing and existing disk image" is listed in virt-install manual on RHEL6, not on RHEL7. Expected results: List "reusing an existing disk image" in virt-install manual on RHEL6. Additional info: