Created attachment 1382760 [details] engine log + print screen Description of problem: Webadmin -> Events -> Events & alerts notifications -> Events -> clear all Error message appears at engine log & in UI ( see print screen) 2018-01-18 09:42:26,452+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.MessageBundler] (default task-8) [1a3585f9-60ac-4938-bb26-20d34ac391a2] Key 'USER_CLEAR_ALL_AUDIT_LOG' is not translated in 'bundles/AuditLogMessages' 2018-01-18 09:42:26,453+02 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [1a3585f9-60ac-4938-bb26-20d34ac391a2] Unable to create AuditLog Version-Release number of selected component (if applicable): 4.2.1.1-0.1.el7 How reproducible: 100% so far Steps to Reproduce: 1.Webadmin -> Events -> Events & alerts notifications -> Events -> clear all Actual results: Error message appears at engine log & in UI ( see print screen) 2018-01-18 09:42:26,452+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.MessageBundler] (default task-8) [1a3585f9-60ac-4938-bb26-20d34ac391a2] Key 'USER_CLEAR_ALL_AUDIT_LOG' is not translated in 'bundles/AuditLogMessages' 2018-01-18 09:42:26,453+02 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [1a3585f9-60ac-4938-bb26-20d34ac391a2] Unable to create AuditLog Expected results: Additional info:
Looks like the complaining class is ClearAllAuditLogAlertsCommand.java or ClearAllAuditLogEventsCommand.java Since it's a backend bundle, moving to infra. I think Ravi is most familiar with this
Verified in ovirt-engine-4.2.2-0.1.el7.noarch ovirt-engine-webadmin-portal-4.2.2-0.1.el7.noarch No exception occurs in browser or ui.log after clicking 'Clear All' for Events in the Notification Drawer. Alerts / Clear All is also OK.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.