Fix tier selection when using different units. #13593
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem was
Rates are tiered. Tier is selected based on the metrics' value.
When metric value and tier boundaries were in different units (metric in bytes, tiers in gigabytes), the tier selection was broken. We used
/
operator instead of*
.Cause
This problem existed since the day 0. It became just more visible after recent refactoring in #13331. I noticed that on one ocasion we had
value * rate_adjustment
and on another occasion we hadvalue / rate_adjustment
. That begged for investigation.@miq-bot add_label chargeback, wip, bug
@miq-bot assign @gtanzillo