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.
Created attachment 527194[details]
vdsm.log
Description of problem:
When moving VM from one data domain to another and restarting vdsm causes that images of the VM are still copying. After copy is finished, files and directory stays on target domain. This causes troubles when one wants to move the VM again to that storage, cause the images are already there.
Version-Release number of selected component (if applicable):
vdsm-4.9-106.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Have a VM with disk, two data storage domains in data-center
2. Move VM
3. During moving restart vdsm on SPM
Actual results:
On NFS you can see that image file grows on storage (being copied) after task fails in rhevm. On target domain leftovers are not removed.
Expected results:
Leftovers are removed when task fails
Additional info:
Relevant for both block and file domains.
vdsm log attached
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/RHSA-2012-1508.html
Created attachment 527194 [details] vdsm.log Description of problem: When moving VM from one data domain to another and restarting vdsm causes that images of the VM are still copying. After copy is finished, files and directory stays on target domain. This causes troubles when one wants to move the VM again to that storage, cause the images are already there. Version-Release number of selected component (if applicable): vdsm-4.9-106.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Have a VM with disk, two data storage domains in data-center 2. Move VM 3. During moving restart vdsm on SPM Actual results: On NFS you can see that image file grows on storage (being copied) after task fails in rhevm. On target domain leftovers are not removed. Expected results: Leftovers are removed when task fails Additional info: Relevant for both block and file domains. vdsm log attached