Conversation
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #12990 +/- ##
============================================
- Coverage 18.00% 18.00% -0.01%
+ Complexity 16466 16465 -1
============================================
Files 5977 5977
Lines 537777 537777
Branches 66037 66037
============================================
- Hits 96844 96843 -1
Misses 430011 430011
- Partials 10922 10923 +1
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:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17435 |
|
@GaOrtiga as this is a simple bug fix, could you target 4.20 instead? |
8f91f45 to
f82db1b
Compare
|
@blueorangutan package |
|
@DaanHoogland 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 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17480 |
Description
When using IPMI, the password is censored before being shown in the logs, this censorship, however, filters for the
-Pparameter, ignoring case. This causes the port to be censored for no reason, as its parameter is-p. This PR uncensors the port while maintaining the censorship on the password, as well as fixes a typo in the method's name.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
The logs changed are used in two places, I checked both instances and verified that the port was no longer censored but the password still was.
How did you try to break this feature and the system with this change?