Bug 2044277
| Summary: | Replace ovirt-engine-extension-logger-log4j with internal ovirt-engine implementation | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Perina <mperina> | |
| Component: | ovirt-engine | Assignee: | Martin Perina <mperina> | |
| Status: | CLOSED ERRATA | QA Contact: | Guilherme Santos <gdeolive> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.4.9 | CC: | apinnick, emarcus, gdeolive, michal.skrivanek, mkalinin, mtessun, nsednev, pelauter, rmcswain, sbonazzo, snikolov | |
| Target Milestone: | ovirt-4.4.10-1 | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.4.10.6 | Doc Type: | Removed functionality | |
| Doc Text: |
With this release, the ovirt-engine-extension-logger-log4j package has been removed. It is replaced by an internal ovirt-engine implementation.
When upgrading from earlier Red Hat Virtualization versions to RHV 4.4.10, the ovirt-engine-extension-logger-log4j package is uninstalled if it is present. If you used the ovirt-engine-extension-logger-log4j in earlier Red Hat Virtualization versions, you must manually remove the ovirt-engine-extension-logger-log4j configuration files and configure the new feature for sending log records to a remote syslog service, as outlined in the Administration Guide.
After a successful upgrade to RHV 4.4.10, you can uninstall log4j12 without breaking the Red Hat Virtualization setup by running the following command: `$ dnf remove log4j12`.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2045913 (view as bug list) | Environment: | ||
| Last Closed: | 2022-02-08 16:57:32 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2033534, 2042344, 2045913, 2046095 | |||
|
Description
Martin Perina
2022-01-24 11:02:32 UTC
Verified on: ovirt-engine-4.4.10.6-0.1.el8ev.noarch ovirt-engine-extension-logger-log4j not present on new installations of RHV and on upgrade from previous versions where it was present. Also, log4j12 can be remove from the machine without interfering with the engine Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: RHV Manager (ovirt-engine) security update [ovirt-4.4.10-1]), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0475 Do we need a doc bug explaining how to reconfigure the syslog configurations to work after the successor of ovirt-engine-extension-logger-log4j will take its part in reporting engine logs to syslog remote server or we're terminating this functionality and syslog server won't be supported anymore? How customers should handle upgrade flow with deployed engine<= 4.4.9 with this extension and configured to forward the logs to some syslog server, then upgrade the engine to >= 4.4.10, log forwarding might be broken. Obsoleting ovirtt-engine-extension-logger-log4j should be mentioned in 4.4.10 release notes and also relevant administration guide has been updated: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/chap-log_files#Enabling_SyslogHandler_RHV_Manager_logs |