| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
All classes that could have their loggers inherited from their fathers had their own loggers deleted; Most loggers didn't have to be static, so most of them were normalized so that they wouldn't be; All loggers are protected now; Static logger's name are now 'LOGGER'; Non-static logger's name are now 'logger'; New class DbUpgradeAbstractImpl created so that all Upgraders extend it and inherit its logger
|
@DaanHoogland @GutoVeronezi could you please review? |
Sorry, something went wrong.
…he last configuration files
|
@JoaoJandre , I didn´t yet review 2000 files, but on first sight it looks good. I hope you have scripts to regenerate the changes, because this PR will be a conflict magnet. |
Sorry, something went wrong.
Codecov ReportAttention: 271 lines in your changes are missing coverage. Please review.
@@ Coverage Diff @@
## main #7131 +/- ##
============================================
- Coverage 30.94% 30.77% -0.18%
+ Complexity 34219 33070 -1149
============================================
Files 5353 5352 -1
Lines 375914 374419 -1495
Branches 54634 54609 -25
============================================
- Hits 116338 115221 -1117
+ Misses 244301 243889 -412
- Partials 15275 15309 +34
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Sorry, something went wrong.
auch, I checked the security issues and marked them safe. @JoaoJandre can you go through the vulnerabilities and bugs, please. I think we must ignore the code smells for this PR. We can sample them but this is going to be a manyear of work to clear them all, even the more serious ones. |
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
shall we keep count @JoaoJandre ? first conflict. (/me joking, let's not!) |
Sorry, something went wrong.
I think it's best we don't keep :D. Sounds great, I'll try to be as fast as possible in completing this PR and addressing any reviews and conflicts.
Sure, I'll go through them. |
Sorry, something went wrong.
@DaanHoogland, as this PR touched a lot of lines, any "bugs" or "vulnerabilities" that already existed are now being reported by Sonarcloud. I fixed one of them that I deemed relevant to this PR; however, in order to avoid raising the complexity of this PR, I think it would be better to create another PR to fix the other bugs and vulnerabilities. What do you think? |
Sorry, something went wrong.
…variable that was mistakenly renamed on the normalization commit
Where it comes to code smells i would agree, but I would rather assess all bugs and vulnerabilities maybe even before merging this. |
Sorry, something went wrong.
|
I updated the SnpmTrapAppender to work with log4j2 and have already tested if it gets created, and if its append method is called; however I did not test the SNMP functionality as it was not changed. I removed the TestAppender, as it was only being used in a single test in a single class, and have rewritten the test. About the AlertSyslogAppender, I have spent some time analyzing it, and it just does not seem to work at all. It will only append if _syslogAppenders is not empty nor null, but as far as I know this attribute cannot be configured via XML, and it is not being set anywhere else in the code, aside from a test class. @DaanHoogland, do you know how to configure and use this appender? If indeed it has never worked properly, could we remove it entirely? |
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-9102)
|
Sorry, something went wrong.
|
[SF] Trillian test result (tid-9104)
|
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
@JoaoJandre 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. |
Sorry, something went wrong.
|
Seems that packaging got stuck on this one; running again: @blueorangutan package |
Sorry, something went wrong.
|
@GutoVeronezi 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. |
Sorry, something went wrong.
might have been just the github api @GutoVeronezi (but rebuilding works;) |
Sorry, something went wrong.
BO seems a bit under the weather today. At first, I thought it could be a problem with the PR; however, I built the packages normally, the tests ran successfully, and other PR's packaging tasks are not being reported as well (vide #8605 (comment)). Any clue if the problem is only with reporting the results? |
Sorry, something went wrong.
@GutoVeronezi @blueorangutan test matrix |
Sorry, something went wrong.
|
@weizhouapache a [SL] Trillian-Jenkins matrix job (centos7 mgmt + xenserver71, rocky8 mgmt + vmware67u3, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-9124)
|
Sorry, something went wrong.
I see, thanks @weizhouapache. |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-9126)
|
Sorry, something went wrong.
|
[SF] Trillian test result (tid-9125)
|
Sorry, something went wrong.
|
Hello guys I checked the test that failed in #7131 (comment), and it seems not related to the PR; therefore, as the last run passed successfully, I will merge this one. If necessary, further improvements or fixes will be addressed in new PRs. A note was already sent in the mailing list notifying the users and devs regarding the next steps; however, if you find someone struggling with the logs or anything that needs adjusting, just ping me or @JoaoJandre, so we can act as fast as possible. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
This PR normalizes ACS's loggers and upgrades log4j 1.2 to log4j 2.19. Back in 2015, PR #714 tried to normalize the loggers but, because that normalization caused some issues with the VMware module, it ended up being reverted. This PR intends to follow that PR's footsteps and normalize all of the loggers in ACS. The objective of reducing unnecessary logger declarations, and reduce the area of impact to upgrade ACS's logger framework from log4j 1.2 to log4 2.19.
The log4j upgrade was done similarly to the proposed here #2992 (comment), and is more detailed ahead.
The logger normalization includes:
BaseElement, PipelineImpl, AbstractRect, AbstractSmartLifeCycle, ManagedContextRunnable, Command, RuleApplier, VmWork, ModelObjectBase, SnapshotStrategyBase, VifDriver.
To normalize all the loggers in ACS, the following steps were performed:
*The ancestor list I created came from a previous iteration of this process, where I tried to simply remove logger instantiation from any class that extended any other class, the list was created while manually fixing the errors.
For the log4j upgrade, the following steps were performed:
If you need to fix conflicts because of this PR, you can try using this script to help you:
About the log4j upgrade:
Disclaimers:
The new log4j2 configuration file format is not backwards compatible with the old one, users must update their configuration files to match with the new format. I used the official apache documentation to upgrade the default configurations, available here.
If you call EncryptorCLI manually, you must also pass the log4j2 jar path (which should be in the same directory as cloud-utils).
The are still some points to address/discuss in order to make this PR ready:
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I tested if both the console and the file appenders were logging correctly in the management server, agents, and system VMs.