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 of problem:
Creating snapshots of thin volumes from Cockpit doesn't work anymore. The error message is
Error creating snapshot: Process reported exit code 3: --size may not be
zero. Run `lvcreate --help' for more information.
The reason is that CreateSnapshot fails to initialize data.new_lv_size when its size argument is zero.
Version-Release number of selected component (if applicable):
udisks2-2.8.0-2.el8.x86_64
How reproducible:
Always for me, but it depends on unitialized memory
Steps to Reproduce:
1. vgcreate TEST /dev/sda
2. lvcreate TEST --thinpool pool -L 20m
3. lvcreate -T TEST/pool -n thin -V 100m
4. gdbus call -y -d org.freedesktop.UDisks2 -o /org/freedesktop/UDisks2/lvm/TEST/thin -m org.freedesktop.UDisks2.LogicalVolume.CreateSnapshot snap 0 '{}'
Error: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error creating snapshot: Process reported exit code 3: --size may not be zero.
Actual results:
Calling CreateSnapshot fails with the error shown above.
Expected results:
the call should succeed.
Additional info:
See https://github.com/storaged-project/udisks/pull/617 for a fix.
Comment 2guazhang@redhat.com
2019-06-19 03:41:24 UTC
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://access.redhat.com/errata/RHBA-2019:3459
Description of problem: Creating snapshots of thin volumes from Cockpit doesn't work anymore. The error message is Error creating snapshot: Process reported exit code 3: --size may not be zero. Run `lvcreate --help' for more information. The reason is that CreateSnapshot fails to initialize data.new_lv_size when its size argument is zero. Version-Release number of selected component (if applicable): udisks2-2.8.0-2.el8.x86_64 How reproducible: Always for me, but it depends on unitialized memory Steps to Reproduce: 1. vgcreate TEST /dev/sda 2. lvcreate TEST --thinpool pool -L 20m 3. lvcreate -T TEST/pool -n thin -V 100m 4. gdbus call -y -d org.freedesktop.UDisks2 -o /org/freedesktop/UDisks2/lvm/TEST/thin -m org.freedesktop.UDisks2.LogicalVolume.CreateSnapshot snap 0 '{}' Error: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error creating snapshot: Process reported exit code 3: --size may not be zero. Actual results: Calling CreateSnapshot fails with the error shown above. Expected results: the call should succeed. Additional info: See https://github.com/storaged-project/udisks/pull/617 for a fix.