Fix error message for checkVolume command - #8842
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #8842 +/- ##
============================================
+ Coverage 30.13% 30.99% +0.85%
- Complexity 33072 34372 +1300
============================================
Files 5355 5355
Lines 376690 376691 +1
Branches 54815 54815
============================================
+ Hits 113533 116742 +3209
+ Misses 248185 244583 -3602
- Partials 14972 15366 +394
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@blueorangutan package |
|
@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9072 |
|
@blueorangutan test alma9 kvm-alma9 |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-9628)
|
|
@blueorangutan test alma9 kvm-alma9 |
|
@vishesh92 a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-9670)
|
borisstoyanov
left a comment
There was a problem hiding this comment.
Manually checked, that whenever there is no suitable host to carry out the check the proper error message appears.
Description
This PR fixes the error message shown when the
checkVolumecommand fails.Before:
{ "accountid": "f7a7493c-ecd7-11ee-a883-1e00a700045b", "cmd": "org.apache.cloudstack.api.command.user.volume.CheckAndRepairVolumeCmd", "completed": "2024-03-28T10:34:49+0000", "created": "2024-03-28T10:34:47+0000", "jobid": "6f452658-b61d-4983-9528-87fd4b2f9f29", "jobinstanceid": "2090adf0-5889-4299-95ea-e104074d9e9a", "jobinstancetype": "Volume", "jobprocstatus": 0, "jobresult": { "errorcode": 530, "errortext": "Unexpected exception" }, "jobresultcode": 530, "jobresulttype": "object", "jobstatus": 2, "userid": "f7a84e5a-ecd7-11ee-a883-1e00a700045b" }After:
{ "accountid": "f7a7493c-ecd7-11ee-a883-1e00a700045b", "cmd": "org.apache.cloudstack.api.command.user.volume.CheckAndRepairVolumeCmd", "completed": "2024-03-28T10:34:49+0000", "created": "2024-03-28T10:34:47+0000", "jobid": "6f452658-b61d-4983-9528-87fd4b2f9f29", "jobinstanceid": "2090adf0-5889-4299-95ea-e104074d9e9a", "jobinstancetype": "Volume", "jobprocstatus": 0, "jobresult": { "errorcode": 530, "errortext": "Unexpected exception: Unable to find Up hosts to run the check volume command" }, "jobresultcode": 530, "jobresulttype": "object", "jobstatus": 2, "userid": "f7a84e5a-ecd7-11ee-a883-1e00a700045b" }Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
checkVolumecommand on a volumeHow did you try to break this feature and the system with this change?