You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Instance snapshot failures when using 'KvmFileBasedStorageVmSnapshotStrategy' #14481
The orphaned row only appears when DefaultVMSnapshotStrategy is excluded (vmSnapshot.strategies.exclude = StorageVMSnapshotStrategy,DefaultVMSnapshotStrategy). With the default strategy enabled, it can delete the Error row; that is also the current workaround (remove it from the exclude list, restart the management servers, delete, restore, restart again).
Cause: KvmFileBasedStorageVmSnapshotStrategy.canHandle(VMSnapshot) returns CANT_HANDLE for any snapshot that is no longer Allocated unless it has the kvmFileBasedStorageSnapshot detail, and that detail is only persisted after a successful create. So the strategy that created the row refuses its own failed row, and VMSnapshotManagerImpl.findVMSnapshotStrategy throws "Can't find Instance Snapshot strategy". deleteAllVMSnapshots propagates this, which is why destroyVirtualMachine fails.
Impact: the row also counts toward vmsnapshot.max, and any user can trigger it (quiescevm=true on a guest without a running agent).
Activity
YanChii commentedon Oct 23, 2026
Hi.
Some context that may help when fixing this:
Jan