Bug 971424
| Summary: | [engine-backend] engine.log is flooded with "No string for UNASSIGNED type. Use default Log" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Idith Tal-Kohen <italkohe> |
| Component: | ovirt-engine | Assignee: | Mooli Tayer <mtayer> |
| Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | acathrow, bazulay, cpelland, ebenahar, eedri, hateya, iheim, jbiddle, jkt, lnatapov, lpeer, lyarwood, pstehlik, Rhev-m-bugs, yeylon, yzaslavs |
| Target Milestone: | --- | Keywords: | Regression, ZStream |
| Target Release: | 3.2.1 | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | infra | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, after upgrading from 3.1 to more recent versions, the engine log would sometimes become flooded by an error message stating "No string for UNASSIGNED type. Use default Log". This was due to an issue with the mechanism in the audit log that prevents multiple messages under the same logType ( e.g command ) from being printed inside a certain time frame.
Now, this has been corrected so that the error message only appears when a message for a logType is not found in AuditLogMessages.properties.
|
Story Points: | --- |
| Clone Of: | 962684 | Environment: | |
| Last Closed: | 2013-07-16 13:40:24 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: | 962684 | ||
| Bug Blocks: | |||
|
Comment 3
Leonid Natapov
2013-06-19 11:48:01 UTC
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1048.html |