| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## 4.22 #14678 +/- ##
=========================================
Coverage 18.32% 18.32%
- Complexity 16644 16647 +3
=========================================
Files 5939 5939
Lines 537787 537787
Branches 65932 65932
=========================================
+ Hits 98544 98553 +9
+ Misses 428033 428023 -10
- Partials 11210 11211 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
|
@vladimirpetrov a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 20019 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
PR #10140 introduced the allocated_size column to the cloud.object_store table, which is expected to hold the sum of all bucket quota, in bytes. To initialize the new column, the following query was introduced:
cloudstack/engine/schema/src/main/resources/META-INF/db/schema-42040to42100.sql
Lines 742 to 749 in f8f3848
However, bucket quotas are stored in GiB, not bytes, and the query does not convert them. As a result, Object Storage providers in environments upgraded from versions prior to 4.21 have an allocated_size that is smaller than expected. When a bucket is deleted, its quota (converted to bytes) is subtracted from this value, which becomes negative. Since the column is unsigned, the update fails and the bucket cannot be deleted:
Impossibility of deleting bucketsTherefore, this PR recalculates the allocated size in bytes for each Object Storage provider. It targets the 4.22.2.0 version. A follow-up PR targeting main will apply the same fix to environments already running 4.23.0.0.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?