Activity log for bug #1592140
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2016-06-13 19:33:17 | Eugene Nikanorov | bug | added bug | ||
2016-06-13 19:37:41 | Bug Checker Bot | tags | need-info | ||
2016-06-16 09:19:09 | Kairat Kushaev | nominated for series | mos/5.1.x | ||
2016-06-16 09:19:09 | Kairat Kushaev | bug task added | mos/5.1.x | ||
2016-06-17 10:08:42 | Kairat Kushaev | mos: importance | Undecided | Medium | |
2016-06-17 10:08:45 | Kairat Kushaev | mos/5.1.x: importance | Undecided | Medium | |
2016-06-17 10:08:52 | Kairat Kushaev | mos: assignee | MOS Glance (mos-glance) | ||
2016-06-17 10:08:58 | Kairat Kushaev | mos/5.1.x: assignee | MOS Glance (mos-glance) | ||
2016-06-17 10:09:41 | Kairat Kushaev | mos: status | New | Confirmed | |
2016-06-17 10:09:43 | Kairat Kushaev | mos/5.1.x: status | New | Confirmed | |
2016-06-17 10:25:54 | Dina Belova | mos: milestone | 5.0-updates | ||
2016-06-17 10:25:57 | Dina Belova | mos/5.1.x: milestone | 5.0-updates | ||
2016-06-17 10:26:17 | Dina Belova | mos/5.1.x: milestone | 5.0-updates | 5.1.1-updates | |
2016-06-17 10:26:19 | Dina Belova | mos: milestone | 5.0-updates | 5.1.1-updates | |
2016-06-17 14:00:59 | Eugene Nikanorov | description | Sometimes when glance-api workers consume lots of memory, client connections could be terminated prematurely. When glance-api is accessed via haproxy, it results in 502 errors given to the client. The only noticable condition is that glance-api processes worked for half a year, and memory consumption has reached 10 Gigs per worker. That might be that eventlet is receiving some sort of system error trying to accept incoming connection. Failed requests never reach glance code itself, therefore they are never logged. | Sometimes when glance-api workers consume lots of memory, client connections could be terminated prematurely. When glance-api is accessed via haproxy, it results in 502 errors given to the client. The only noticeable condition is that glance-api processes worked for half a year, and memory consumption has reached 10 Gigs per worker. That might be that eventlet is receiving some sort of system error trying to accept incoming connection. Failed requests never reach glance code itself, therefore they are never logged. | |
2016-07-22 00:05:55 | Roman Rufanov | tags | need-info | customer-found need-info support | |
2016-07-26 13:40:55 | Kairat Kushaev | mos: status | Confirmed | Invalid | |
2016-07-26 13:41:00 | Kairat Kushaev | mos/5.1.x: status | Confirmed | Invalid |