liberasure produces unnecessary messages in user.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Medium
|
Alexey Stupnikov | ||
10.0.x |
Won't Fix
|
Medium
|
MOS Swift |
Bug Description
Detailed bug description:
If swift is installed liberasure produces the following messages every 5 minutes that end up being written to /var/log/user.log:
<11>Dec 6 16:30:02 node-6 liberasurecode[
<11>Dec 6 16:30:02 node-6 liberasurecode[
<11>Dec 6 16:30:02 node-6 liberasurecode[
<11>Dec 6 16:30:02 node-6 liberasurecode[
As I understand messages generated because on liberasure pluggable architecture which tries to use all backend plugins even if they aren't installed.
This issue looks cosmetic but nevertheless log files filled with unnecessary messages could be quite disturbing.
Steps to reproduce:
Deploy MOS with Swift
Expected results:
liberasure produces only relevant messages
Actual result:
liberasure complain about missing shared objects every 5 minutes
Reproducibility:
All the time
Workaround:
Syslog could be configured to write liberasure logs in separate file (or ignore them)
Impact:
Cosmetic
Description of the environment:
- Operation system: MOS 9.0, Ubuntu 14.04
- Related projects installed: Swift
Changed in mos: | |
status: | New → Confirmed |
assignee: | nobody → MOS Swift (mos-swift) |
milestone: | none → 10.0 |
tags: | added: sla2 |
tags: | removed: sla2 |
Changed in mos: | |
assignee: | MOS Swift (mos-swift) → Alexey Stupnikov (astupnikov) |
no longer affects: | mos/9.x |
Changed in mos: | |
status: | Confirmed → In Progress |
Changed in mos: | |
status: | In Progress → Fix Committed |
Changed in mos: | |
status: | Fix Committed → In Progress |
Changed in mos: | |
milestone: | 9.2-mu-3 → 9.x-updates |
I have another customer case with similar issue. This appears to have been fixed in the pyeclib code as follows: https:/ /bitbucket. org/kmgreen2/ pyeclib/ commits/ 4f278195a42ea0f 254114c92043b6b a6ecdc6b0a