New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change exception when orchestrating VM start #9062
base: main
Are you sure you want to change the base?
Change exception when orchestrating VM start #9062
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm. didn't test.
@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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9062 +/- ##
============================================
+ Coverage 15.28% 16.02% +0.73%
- Complexity 11523 11537 +14
============================================
Files 5425 5062 -363
Lines 474008 444573 -29435
Branches 61750 54378 -7372
============================================
- Hits 72445 71234 -1211
+ Misses 393518 365414 -28104
+ Partials 8045 7925 -120
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9588 |
@blueorangutan test |
@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
[SF] Trillian Build Failed (tid-10211) |
[SF] Trillian test result (tid-10242)
|
Description
When attempting to start a VM, if an error occurs, the exception displayed to users is the same as what is being logged, which can expose information about the environment.
This PR addresses this issue by keeping the current message to be sent to the logs and adding a new one for the exception shown to users.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
Exception before the proposed changes
Exception after the proposed changes
How Has This Been Tested?
Using a stopped VM, I changed the Compute Offering to a offering with
Host Tags
incompatible with every host in my environment in order to force the exception, then I tried to start the VM. An exception was thrown as shown in the screenshots above.I also checked the logs in both cases and the only changes was log level and the removal of a duplicated message at the end of the log related to the exception.
Old log:
New log: