ui: label instance volume sizes as GiB - #13831
Conversation
|
Please build the exact PR head for QA validation: |
|
@Dogface2k a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
QA validation completed against exact PR head
Local gates recorded in the PR description remain passing: focused regression, full UI unit suite, lint, and production build. |
|
Unit check: issue #13820 asks for a consistent and correct label. Both views divide the API byte count by |
|
Please rebuild the exact new PR head for QA validation: |
|
@Dogface2k a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
QA validation for exact head
Local validation on this exact head: 178 UI unit tests passed, lint passed, and the production build completed successfully. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13831 +/- ##
=========================================
Coverage 17.69% 17.70%
- Complexity 15835 15836 +1
=========================================
Files 5925 5925
Lines 533539 533539
Branches 65274 65274
=========================================
+ Hits 94427 94466 +39
+ Misses 428435 428389 -46
- Partials 10677 10684 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|

Fixes #13820.
Summary
Use the correct
GiBunit for byte-derived volume sizes across the affected UI paths:GiB Storage).This keeps the displayed unit consistent anywhere these API byte counts are rendered.
Root cause
These paths divide byte counts by
1024³, which is a binary conversion to gibibytes. The old labels saidGB, implying decimal gigabytes. The numeric conversion and API behaviour are unchanged.Tests
GBoutput and expectsGiB.Validation
c2c6fe8a29fb47bfb224bb99360f6571b51126c3. Firefox verified the instance Volumes tab row forROOT-1369renders0.00 GiB; noGBlabel appeared in that row.volumescollection, so the summary-card branch was not rendered there. It exposed no backup detail fixture, so that branch was not rendered there. Both remain covered by focused unit tests and the production build.Scope
Only existing labels and focused component tests changed. No API, numeric conversion, provisioning, or CloudStack resource behavior changed.