Apache graceful restart leads to mod_wsgi segfault
Bug #1493353 reported by
Vladimir Kuklin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Critical
|
Vladimir Kuklin | ||
6.1.x |
Invalid
|
Undecided
|
Vladimir Kuklin | ||
7.0.x |
Won't Fix
|
High
|
Vladimir Kuklin |
Bug Description
Please look into for details https:/
This needs to be worked around until upstream fix for mod_wsgi is available.
This happens during cluster scale-up/scale-down operations as apache gets reloaded and thus mod_wsgi starts misbehaving which makes deployment fail as we cannot operate with keystone entities.
For details also look into
Changed in fuel: | |
status: | Incomplete → Confirmed |
assignee: | Vladimir Kuklin (vkuklin) → MOS Linux (mos-linux) |
tags: | added: area-library |
no longer affects: | fuel/8.0.x |
Changed in fuel: | |
status: | Incomplete → Won't Fix |
status: | Won't Fix → Invalid |
status: | Invalid → Won't Fix |
tags: |
added: 8.0 release-notes-done removed: release-notes |
To post a comment you must log in.
The workaround is simple - do not reload mod_wsgi so often. As github comments suggest (and my comments in the bug/1490523), there should be at least 1 minute pause before restarts. Or, alternatively, run keystone as a separate process.