The snapshots are configured to be stored on Primary Storage. However, when attempting to create a snapshot, CloudStack still performs validation against the Secondary Storage resource limits.
For example:
- If we have a 10GB volume and attempt to create a snapshot without sufficient secondary storage quota for the domain, the snapshot creation fails.
- This behavior is inconsistent, as the snapshot is supposed to be stored in Primary Storage and should not depend on secondary storage quota validation.
This seems to be an issue in the snapshot workflow where quota checks are incorrectly applied to secondary storage, even when primary storage is used for Snapshot.