rate_limit_except_level is broken in log.py
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.log |
Fix Released
|
High
|
Takashi Kajinami |
Bug Description
In _options.py, you provide a config option called 'rate_limit_
202 cfg.StrOpt(
203 default='CRITICAL',
204 help='Log level name used by rate limiting: CRITICAL, ERROR, '
205 'INFO, WARNING, DEBUG or empty string. Logs with level '
206 'greater or equal to rate_limit_
207 'filtered. An empty string means that all levels are '
208 'filtered.'),
209 ]
But then, over in log.py, when you try to parse this option, you call it by the wrong name in line 453:
453 if conf.rate_
454 from oslo_log import rate_limit
455 rate_limit.
456 conf.rate_
457 conf.rate_
You see the difference between 'rate_limit_
I am attaching a simple patch
Changed in oslo.log: | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Takashi Kajinami (kajinamit) |
I should have added...if this isn't patched, and you include the 'rate_limit_ except_ level' option in nova.conf, then none of your nova services will even start...