ISSUE TYPE

• Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.19

CONFIGURATION

XCP_NG 8, Cloudstack 4.19

OS / ENVIRONMENT

NA

SUMMARY

When a user sets up recurring volume snapshot, if the number of snapshots to keep (example 3) is less than the snapshot.delta.max (example 7), it creates a chain of 7, but the cloud_usage table shows as if the first 4 snapshots were destroyed, while the physically continue to exist and take up secondary storage space. This is creating artifically low secondary storage usage and creates billing challenges as well as shows incorrect information to users.

NOTE - this used to work correctly in 4.17 (I upgraded from 4.17 to 4.19 recently - I skipped 4.18).

STEPS TO REPRODUCE

Set up global config snapshot.delta.max = 7.
Setup a Volume recurring snapshot with Keep = 3 (I only used the Daily option). 
Observe the cloud_usage table. On Fourth day, you will notice that there are 4 physical snapshots present in secondary storage due to chaining, but the usage for 4th day only shows as if 3 were in use. 

EXPECTED RESULTS

The entire snapshot chain should be shown in the cloud_usage for each date regardless of the number of snapshots to keep. 

ACTUAL RESULTS

Only the last 3 snapshots are shown as existing ones.