Description of problem:
We have this test flow to test snapshot merge live that I will describe:
1. Create a vm from a template and add multiple disks (4), create a fs on those disks
2. Start the vm and add 1 file on each disk, create a snapshot (0)
3. add 1 file on each disk, create a snapshot (1)
4. add 1 file on each disk, create a snapshot (2)
5. Delete the middle snapshot (1).
6. Preview snapshot (2) and check the files are there.
This works in base scenario, but it fails when the scenario is from an upgrade from 3.6 to 4.1, files created on step 4 exist but are empty.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
follow what I previously set there.
So if I try to make a memory snapshot of the snapshot (2) it will say:
Custom compatibility version will be set when restoring memory from different cluster version.Previewing memory may cause data loss when excluding disks!
This scenario works on a base case when the env was 4.1 from the beginning, but fails here.
I'll add some logs. The environment were this happen is available with the vms in case you need to take a look.
Created attachment 1248613 [details]
engine.log and vdsm.log
vm name: vm_TestCase6038_REST_ISCSI_081431 vm id: c192bb84-f02a-4fed-a72c-feca7a66801a
snapshot that was preview id: "bb0a69d1-03d7-46c3-8483-f0eb285d9863" description: snapshot_6038_iscsi_2
* In which step did you perform the upgrade?
* IIUC, the issue was in memory snapshot?
(In reply to Daniel Erez from comment #3)
> * In which step did you perform the upgrade?
Before this case run. This was an env that was 3.6 and run our tier1 when we shipped 3.6.10, then it was upgrade to 4.0 and run some automation, finally it got upgrade to 4.1 and has been running our tier1, seeing this failure that I don't see running in a clean 4.1 installation.
> * IIUC, the issue was in memory snapshot?
No, sorry my mistake in the description. The snapshots taken are memory snapshot, the preview of the snapshot is without the memory. I posted the message just because I notice and maybe the custom compatibility message was relevant even if it's not a memory snapshot been previewed.
We couldn't find any unexpected issues in engine nor vdsm. The fact that the files exists on the guest but with empty content hints that this might be a guest issue.
As discussed, can you please reproduce the scenario upgrading from 3.6 to 4.0, and from 4.0 to 4.1, on a clean environment and describe the steps to reproduce.
No update for a while. Closing for now. Please reopen if indeed reproduced.
could not reproduce.