Bucket usage continues even after the bucket is deleted.
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.4k
- Merge moyen
- 6 j 19 h
- PR mergées (30 j)
- 32
Description
### problem
Good afternoon everyone,
I've identified a potential bug in the CloudStack usage section. After deleting a bucket, I noticed that the `cloudstack.listUsageRecords` API call was still reporting usage of the deleted buckets for the accounts.
I started exploring the code and how this bucket usage system works, and I found that it all depends on the `bucket_statistics` table.
From what I understand and replicate in my tests, when a bucket is removed, the `bucket_statistics` table retains the used size value. In my understanding, the correct approach would be to reset this value or delete the record for that bucket in this table. I corrected this in the accounts by resetting the size value, thus stopping the generation of new records in the `cloud_usage` table.
If you have any further questions, feel free to ask and I'll provide more details.
Thank you.
### versions
Cloudstack 4.22
### The steps to reproduce the bug
1. Create a bucket
2. Add data to the bucket
3. Wait a few days for cloud_usage records to be generated
4. Remove the data from the bucket
5. Then remove the bucket from Cloudstack
6. Verify in the listUsageRecords API calls that usage records are still being generated for the bucket.
### What to do about it?
When removing a bucket, the bucket_statistics table retains the used size value; in my understanding, the correct approach would be to reset this value or delete the record for that bucket in this table.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par suivre la suppression du bucket et l’enregistrement bucket_statistics, puis suivez la manière dont cloudstack.listUsageRecords lit cette taille conservée dans les enregistrements cloud_usage. Reproduisez la séquence indiquée sur CloudStack 4.22 et vérifiez que la suppression d’un bucket ne génère plus d’enregistrements d’utilisation pour celui-ci.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- api, cloud, databases
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 66/100