nxsbi opened a new issue, #9416:
URL: https://github.com/apache/cloudstack/issues/9416

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   UI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   XCP_NG 8, Cloudstack 4.19
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   NA
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   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
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   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. 
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   The entire snapshot chain should be shown in the cloud_usage for each date 
regardless of the number of snapshots to keep. 
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Only the last 3 snapshots are shown as existing ones. 
   ~~~
   


-- 
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: commits-unsubscr...@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to