Undefined While digging into the node capacity, I discovered a bug with the cluster capacity.
For example if you group by project:
If only two sources contain that project:
"capacity": { "value":6912.0, "units":"GB-Hours" },
"clusters":[ "Test OCP on AWS", "Test OCP on GCP" ],
"source_uuid":[ "0cea0c29-19f6-4e2e-a9b1-40724be081bb", "43db0118-d299-4bf8-b08d-6d533afc7838" ],
The capacity is the same as when all 4 clusters have that project:
"capacity": { "value":6912.0, "units":"GB-Hours" },
"clusters":[ "Test OCP on AWS", "Test OCP on Azure", "Test OCP on GCP", "Test OCP on Premises" ],
"source_uuid":[ "0cea0c29-19f6-4e2e-a9b1-40724be081bb", "43db0118-d299-4bf8-b08d-6d533afc7838", "4f272ef3-e496-4d2b-be98-0b0f914eab66", "eeadca26-0d11-4057-851c-9bbf0f7e5ac4" ],
After doing some digging I discovered that the "cluster" was never being returned in the row here. Causing the capacity during the annotation to always be the daily sum, which contained all 4 clusters.
- relates to
-
COST-3608 Report vCPU count, RAM and storage capacity on the nodes/instances
-
- Closed
-