WSGI requests in ir-api are reported with no log level and inconsistent date string
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Low
|
Unassigned |
Bug Description
WSGI requests in ir-api are reported with no log level and a date string which is not consistent with the rest of the log:
Example:
2015-10-19 11:30:22.583 18979 DEBUG keystonemiddlew
2015-10-19 11:30:22.584 18979 DEBUG keystonemiddlew
127.0.0.1 - - [19/Oct/2015 11:30:22] "GET /v1/nodes/
2015-10-19 11:30:22.639 18979 DEBUG keystonemiddlew
2015-10-19 11:30:22.641 18979 DEBUG keystonemiddlew
127.0.0.1 - - [19/Oct/2015 11:30:22] "GET /v1/nodes/
2015-10-19 11:30:23.660 18979 DEBUG keystonemiddlew
2015-10-19 11:30:23.662 18979 DEBUG keystonemiddlew
Changed in ironic: | |
assignee: | nobody → Zhenguo Niu (niu-zglinux) |
assignee: | Zhenguo Niu (niu-zglinux) → nobody |
Changed in ironic: | |
assignee: | nobody → Rahul U Nair (rahulunair) |
Changed in ironic: | |
status: | Confirmed → In Progress |
The crux of this issue is that wsgiref. simple_ server is used, which means default logging is very wonky.
http:// stackoverflow. com/questions/ 31433682/ control- wsgiref- simple- server- log - gives some hints on how to do this right.