Bug 1585030
| Summary: | [downstream clone - 4.2.4] RAW-Preallocated disk is converted to RAW-sparse while cloning a VM in file based storage domain | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | vdsm | Assignee: | Nir Soffer <nsoffer> |
| Status: | CLOSED ERRATA | QA Contact: | Shir Fishbain <sfishbai> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0.6 | CC: | achareka, appraprv, dfodor, ebenahar, eshenitz, fcami, lsurette, mzheng, nsoffer, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ycui, ykaul, ylavi |
| Target Milestone: | ovirt-4.2.4 | Keywords: | ZStream |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1429286 | Environment: | |
| Last Closed: | 2018-06-27 10:02:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1429286 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2018-06-01 07:53:02 UTC
We'll probably fix by fallocate() and not the regular 'dd' ? (Originally by Yaniv Kaul) (In reply to Yaniv Kaul from comment #2) > We'll probably fix by fallocate() and not the regular 'dd' ? Agreed, do we have a RFE to block this bug on? (Originally by ylavi) (In reply to Yaniv Dary from comment #3) > (In reply to Yaniv Kaul from comment #2) > > We'll probably fix by fallocate() and not the regular 'dd' ? > > Agreed, do we have a RFE to block this bug on? https://bugzilla.redhat.com/1391859 (Originally by Yaniv Kaul) This is partly a duplicate of 1532133. We have several flows when cloning images: - Collapsing the original chain to single volume - uses Volume.copy. It needs a similar fix to the one applied for bug 1532133. - Copying all volumes to target image, cluster version 4.1 - uses SDM.copy_data these patches handle the vdsm side: https://gerrit.ovirt.org/#/q/topic:copy-data-prealloc More work is needed for engine side. - Copying all volumes to target image, cluster version < 4.1 - uses Image.move, it is already fixed by the fix to bug 1532133. (Originally by Nir Soffer) *** Bug 1403183 has been marked as a duplicate of this bug. *** (Originally by Eyal Shenitzky) (In reply to Nir Soffer from comment #5) > This is partly a duplicate of 1532133. > > We have several flows when cloning images: > > - Collapsing the original chain to single volume - uses Volume.copy. It > needs a > similar fix to the one applied for bug 1532133. > > - Copying all volumes to target image, cluster version 4.1 - uses > SDM.copy_data > these patches handle the vdsm side: > https://gerrit.ovirt.org/#/q/topic:copy-data-prealloc > More work is needed for engine side. > > - Copying all volumes to target image, cluster version < 4.1 - uses > Image.move, > it is already fixed by the fix to bug 1532133. This bug fix refers to the following flows: - Clone VM - Copy (floating/VM/template) disk - Clone VM from a snapshot - Import VM from an export domain - Create VM template - Create VM template from a snapshot I've open new bug 1571285 to track the solution for cold storage migration that uses SDM.copy_data on vdsm - https://gerrit.ovirt.org/#/q/topic:copy-data-prealloc (Originally by Eyal Shenitzky) WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops
(Originally by rhv-bugzilla-bot)
When creating new image, the new image is exactly the same as the original VM. 4.2.4.2-0.1 version 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/RHEA-2018:2072 BZ<2>Jira Resync sync2jira sync2jira |