rajujith opened a new issue, #14481:
URL: https://github.com/apache/cloudstack/issues/14481
### problem
Instance snapshots fail to create and also fail to delete; further, it
becomes unable to destroy the Instance altogether.
```
| setting | value |
|---|---|
| `vmSnapshot.strategies.exclude` |
`StorageVMSnapshotStrategy,DefaultVMSnapshotStrategy` |
| `kvm.vmstoragesnapshot.enabled` | `false` |
| `vmsnapshot.max` | `10` (default) |
```
### versions
4.22.1.1
### The steps to reproduce the bug
1. A running KVM instance on NFS primary storage, no volume snapshots, no
Instance Snapshots.
2. Stop the QEMU guest agent inside the guest (or use a guest that has none
installed).
3. As the owning user: `createVMSnapshot virtualmachineid=<vm>
snapshotmemory=false quiescevm=true`
→ fails (expected — quiesce needs the agent).
4. `listVMSnapshot virtualmachineid=<vm>` → the attempt is listed with
`state: Error`.
5. `deleteVMSnapshot vmsnapshotid=failed vmsnapshotid` (as the user, and
again as root admin) → `Failed to delete Instance Snapshot`.
6. `destroyVirtualMachine id=<vm> expunge=true` (root admin) → `Failed to
destroy vm with specified vmId`;
the instance ends up `Stopped`, not destroyed.
Retrying step 3 with `quiescevm=false` succeeds, so the snapshot capability
itself is fine — only
the failed attempt's Instance snapshot is orphaned.
### What to do about it?
The failure scenario should be either fixed or handled gracefully
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
