| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Signed-off-by: xujiantop-crypto <265865031+xujiantop-crypto@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## 4.20 #14114 +/- ##
============================================
+ Coverage 16.36% 16.37% +0.01%
- Complexity 13592 13599 +7
============================================
Files 5669 5669
Lines 501475 501475
Branches 60913 60913
============================================
+ Hits 82067 82128 +61
+ Misses 410209 410137 -72
- Partials 9199 9210 +11
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.
|
can you put some UI screenshots where you find these workflows working? |
Sorry, something went wrong.
|
tested by reporter (see #14103 (comment)) |
Sorry, something went wrong.
There was a problem hiding this comment.
clgtm
Sorry, something went wrong.
| if (userVmDetails != null) { | ||
| String minIops = userVmDetails.get(MIN_IOPS); | ||
| String maxIops = userVmDetails.get(MAX_IOPS); | ||
| String minIops = userVmDetails.get(VmDetailConstants.MIN_IOPS); |
There was a problem hiding this comment.
should the min and max check on deploy use these new names too? it still looks up the old ones, so a min above max now reaches the volume without an error
Sorry, something went wrong.
There was a problem hiding this comment.
@Damans227 what change are you suggesting (if any)?
Sorry, something went wrong.
There was a problem hiding this comment.
the check that stops a min above max on deploy is in UserVmManagerImpl, and it still looks up miniops and maxiops. i suggest it reads the new minIops and maxIops names too, so a bad pair errors out instead of reaching the volume.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Custom root disk IOPS are stored in VM details as minIops and maxIops. CloudOrchestrator was reading the API parameter names miniops and maxiops, so the values were not propagated to the root DiskOfferingInfo during VM deployment from a template.
This change:
Fixes #14103
Testing