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:
Currently (using the LivePayload) the contents of an image can be transfered to a newly created filesystem using rsync (IIRC).
As ovirt-node is moving to anaconda, and we want to stick with images, we'll need a way to transfer an image byte by byte to a logical volume.

Additional info:
Another change is needed to create a writable thin-volume snapshot atop the populated thin logical volume.

Using the liveimg kickstart command you can use a variety of sources for the images including squashfs, mountable filesystem images and tar.bz2 trees.

I am opposed to returning to the days of byte-by-byte copies and then resizing things.

The current methods are much more flexible, allowing you to deploy images onto a variety of target filesystems instead of being locked into the source's filesystem type.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

If this is reconsidered, the it would also be good to support "streaming" binary images to disk, to prevent a problem when the filesystem images are to large.