keystone eventlet should never be started
Bug #1572283 reported by
Emilien Macchi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Cloud Archive |
Won't Fix
|
Medium
|
Corey Bryant | ||
Bug Description
Deploying keystone on trusty, using UCA / mitaka:
eventlet process tries to start, while Keystone team dropped eventlet support.
We should not start this process, it's very dangerous, for deployments that deploy Keystone with mod_wsgi in Apache (recommended).
Revision history for this message
| Corey Bryant (corey.bryant) wrote | #1 |
| Changed in cloud-archive: | |
| assignee: | nobody → Corey Bryant (corey.bryant) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in cloud-archive: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| James Page (james-page) wrote | #3 |
To post a comment you must log in.
keystone-all is still shipped by upstream in Mitaka, and while it's preferred to run under mod_wsgi, we can't make this change 2 days prior to release of 16.04. I'm targeting this change for 16.10 to coincide with OpenStack Newton.