[Usage] Fix wrong usage_type#7229
Conversation
Codecov Report
@@ Coverage Diff @@
## main #7229 +/- ##
============================================
- Coverage 12.67% 12.67% -0.01%
Complexity 8641 8641
============================================
Files 2716 2716
Lines 256112 256111 -1
Branches 39926 39926
============================================
- Hits 32461 32460 -1
Misses 219522 219522
Partials 4129 4129
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
1 similar comment
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
|
Kudos, SonarCloud Quality Gate passed! |
stephankruggg
left a comment
There was a problem hiding this comment.
CLGTM, not manually tested
|
|
||
|
|
||
| -- Change usage of VM_DISK_IO_WRITE to use right usage_type | ||
| UPDATE | ||
| `cloud_usage`.`cloud_usage` | ||
| SET | ||
| usage_type = 22 | ||
| WHERE | ||
| usage_type = 24 AND usage_display like '% io write'; No newline at end of file |
There was a problem hiding this comment.
As the milestone changed to version 4.18.1.0 this needs to be changed to the correct schema file.
There was a problem hiding this comment.
@BryanMLima
I think this can be merged into 4.18.0.0








Description
IO write events have been saved in the database using the
usage_typeof theVM_DISK_BYTES_WRITEtype, which causes an inconsistency in the database. This behavior has been fixed by this PR. Plus, the old data saved in the database has been normalized.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
It was tested in a local lab: