-
Notifications
You must be signed in to change notification settings - Fork 1.2k
VMware import - logs sanitation #10433
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
VMware import - logs sanitation #10433
Conversation
|
@blueorangutan package |
|
@sureshanaparti 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. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #10433 +/- ##
============================================
- Coverage 15.17% 15.16% -0.01%
+ Complexity 11340 11336 -4
============================================
Files 5414 5414
Lines 475093 475084 -9
Branches 57971 57970 -1
============================================
- Hits 72086 72069 -17
- Misses 394945 394956 +11
+ Partials 8062 8059 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@kiranchavala 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. |
|
@blueorangutan package |
|
@sureshanaparti 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]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12522 |
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
efc7b08 to
51af846
Compare
|
@blueorangutan package |
|
@sureshanaparti 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]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13258 |
DaanHoogland
left a comment
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
|
@blueorangutan package |
|
@rohityadavcloud 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]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13308 |
kiranchavala
left a comment
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.
LGTM
Before fix
Cloudstack was logging the vcenter credentials
2025-05-15 12:34:05,970 DEBUG [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (agentRequest-Handler-1:[]) (logid:edec8444) Executing command [ovftool --noSSLVerify vi://administrator%40vsphere.local:P%[email protected]/Trillian/vm/e552b5c2-f4d3-4c15-93a1-6a2c560df142 /mnt/a1047887-9e10-3157-9336-432b0b47ecfe/01a1d8ab-e41f-4fc6-a288-aac8b787a100/ ].
After fix
2025-05-15 11:54:53,033 DEBUG [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (agentRequest-Handler-4:null) (logid:0fa4514f) Executing command [ovftool --noSSLVerify vi://******@10.0.35.100/Trillian/vm/5cbc76b0-feaf-40ab-ac0d-4abb09b72885 /mnt/f30da0ff-56c0-364d-9146-caa63d6d3de0/0c73a2e1-4113-423b-8359-958d41635464/ ]
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-13323)
|
Description
This PR sanitises logs of ovftool cmd during vmware import.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Manually tested, and checked the logs.
How did you try to break this feature and the system with this change?