GitHub user boubouX added a comment to the discussion: Volume Stuck in Snapshotting
Hello prashanthr2, Thank you for your response. My best guess is that the issue occurred because the account or domain temporarily ran out of secondary storage capacity quota, which has since been resolved. Here is the current status: 1. The VM is working as expected. 2. A snapshot of its volume is in the Creating state, with a DAILY interval type, created on October 19. 3. The VDI is 250 GB, stored locally on the KVM host in QCOW2 format. It is not shown as snapshotted when checked via qemu-img info. 4. A manual reverse database lookup from the VDI path returns the unexpected VM name “ABTWDCAPP01” instead of the expected “TS02”. “ABTWDCAPP01” does not appear in the web UI. 5. In the web UI, the volume state is “Snapshotting.” It shows no metrics collected, which is unusual, and a SNAPSHOT.CREATED event is logged every 5 minutes. 6. Every 5 minutes, the Management Server logs the following error: ``` 2025-10-28 06:35:24,718 ERROR [c.c.s.s.SnapshotSchedulerImpl] (SnapshotPollTask:ctx-7fdc17a1) (logid:d13be60e) The scheduling of snapshot [6763e09b-dd3b-4ff4-b1fd-1046d0dbb681] for volume [147] failed due to [com.cloud.exception.InvalidParameterValueException: VolumeId: 147 is not in Ready state but Snapshotting. Cannot take snapshot.]. ``` 7. The environment is running Apache CloudStack 4.19.3, and the Management Server was last rebooted about a day ago. 8. I can shut down the VM in about 16 hours for further investigation. Do you have any suggestions for the next steps? Best regards GitHub link: https://github.com/apache/cloudstack/discussions/11915#discussioncomment-14803108 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
