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.
+++ This bug was initially created as a clone of Bug #755596 +++
Description of problem:
All rollbacks should be saved persistently on the disk after every change (especially after remove/clear recoveries)
Version-Release number of selected component (if applicable):
How reproducible:
Restart SPM during merge snapshots of large disks (with postzeroing), SPM will switched to another host and rollback the operation
Steps to Reproduce:
1. Two hosts, VM with snapshots and large disks (with postzeroing)
2. VM should be with RAW base volume (not template) and snapshot on it
3. Start delete snapshot and look for dd start in vdsm log
4. restart vdsm on SPM host
5. SPM will switch to another host and start rollbacks
Actual results:
Image will broken
Expected results:
No rollback should occurs on new SPM .
Additional info:
--- Additional comment from danken on 2011-11-21 10:21:42 EST ---
http://gerrit.ovirt.org/303