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.
Description
The usage of manual doc and error message about 'sparse' are different in virt-install
For the usage about 'sparse' of manual doc in virt-install:
...
sparse
whether to skip fully allocating newly created storage. Value is ’true’ or ’false’. Default is ’true’ (do not fully allocate).
...
But when use '--nonsparse' with '--disk' parameters,
Error message would be pop up as:
ERROR Cannot mix --file, --nonsparse, or --file-size with --disk options. Use --disk PATH[,size=SIZE][,sparse=yes|no]
The two usages should be consistent, sparse=yes|no or sparse=true|false.
Version
python-virtinst-0.600.0-12.el6.noarch
libvirt-0.10.2-7.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Check manual doc of virt-install about sparse, check the usage explanation.
2. Use "--nonsparse" with "--disk" at the same time
virt-install -n demo2 -r 512 -l http://tree.englab.nay.redhat.com/pub/rhel/released/RHEL-6/6.3/Server/x86_64/os/ --disk path=/var/lib/libvirt/images/demo2.img,size=5 --nonsparse
check the error message.
3. Compare the usage of manual doc and error message about 'sparse'
Actual results：
The usage were inconsistent,
In manual doc, which should used as "--disk ...,sparse=false,..."
But in error message, which hint Use "...--disk PATH[,size=SIZE][,sparse=yes|no]"
Expected results:
The usage should be consistent
Additional info:
Both of the usage "sparse=no" and "sparse=false" did not work.
There is a bug for this issue:https://bugzilla.redhat.com/show_bug.cgi?id=873545
Description The usage of manual doc and error message about 'sparse' are different in virt-install For the usage about 'sparse' of manual doc in virt-install: ... sparse whether to skip fully allocating newly created storage. Value is ’true’ or ’false’. Default is ’true’ (do not fully allocate). ... But when use '--nonsparse' with '--disk' parameters, Error message would be pop up as: ERROR Cannot mix --file, --nonsparse, or --file-size with --disk options. Use --disk PATH[,size=SIZE][,sparse=yes|no] The two usages should be consistent, sparse=yes|no or sparse=true|false. Version python-virtinst-0.600.0-12.el6.noarch libvirt-0.10.2-7.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Check manual doc of virt-install about sparse, check the usage explanation. 2. Use "--nonsparse" with "--disk" at the same time virt-install -n demo2 -r 512 -l http://tree.englab.nay.redhat.com/pub/rhel/released/RHEL-6/6.3/Server/x86_64/os/ --disk path=/var/lib/libvirt/images/demo2.img,size=5 --nonsparse check the error message. 3. Compare the usage of manual doc and error message about 'sparse' Actual results： The usage were inconsistent, In manual doc, which should used as "--disk ...,sparse=false,..." But in error message, which hint Use "...--disk PATH[,size=SIZE][,sparse=yes|no]" Expected results: The usage should be consistent Additional info: Both of the usage "sparse=no" and "sparse=false" did not work. There is a bug for this issue:https://bugzilla.redhat.com/show_bug.cgi?id=873545