Failed to revert a memory snapshot

[poli1025]

problem

Unable to revert a disk and memory snapshot if a disk-only snapshot already exists.

Expected Result:
The disk and memory snapshot should be restored successfully.

Actual Result:
Restoration fails when a disk-only snapshot exists prior to the disk and memory snapshot ,but works without issues if the machine has not been powered off.

versions

Cloudstack 20.0.1
Hypervisor kvm
SO ubuntu24.0.4

The steps to reproduce the bug

1. Create a snapshot without memory.
2. Create a snapshot including both disk and memory.
3. Power off the virtual machine.
4. Power on the virtual machine.
5. Attempt to revert the disk and memory snapshot.

What to do about it?

No response

[github-actions[bot]]

This issue is stale because it has been open for 120 days with no activity. It may be removed by administrators of this project at any time. Remove the stale label or comment to request for removal of it to prevent this.

[DaanHoogland]

@poli1025 , it seems your issue finds no traction. Do you care to work on it some more, or shall we close it?

If you can add more information (from logs for instance, or DB info) it might encourage people to work on it.

[weizhouapache]

according to #11039, external and internal snapshots can not work together.

[DaanHoogland]

@weizhouapache does it make sense to enforce this somehow in API and/or UI. It is a bit harsh to find you cannot use a snapshot on restoring, better to be alerted while creating.

[weizhouapache]

@weizhouapache does it make sense to enforce this somehow in API and/or UI. It is a bit harsh to find you cannot use a snapshot on restoring, better to be alerted while creating.

with #11039, user should not be able to create both snapshots. I do not know why these two steps worked

1. Create a snapshot without memory.
2. Create a snapshot including both disk and memory.

[DaanHoogland]

ok, well, #11039 is on main/23 not on the reported 4.20.

[weizhouapache]

ok, well, #11039 is on main/23 not on the reported 4.20.

oh really ?
#10632 was merged into 4.21, not 4.20