gunicorn worker timeout blocks appliance config update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Astara |
Fix Released
|
Medium
|
Adam Gandelman | ||
akanda |
Fix Released
|
Medium
|
Adam Gandelman |
Bug Description
this is probably only an issue in dev environments where we're running the appliance /w non-accelerated nested virt, which describes where the devstack gate jobs run.
in such envs, the appliance tries to restart the metadata service as part of its config update. this can take a long time, sometimes >=a 30s, which is the default gunicorn worker timeout. in the devstack slaves, it appears to consistently take longer than 30s causing the config updates to fail with a BadStatusLine error on the client (rug) side, ie http://
2015-06-03 23:40:18:
Traceback (most recent call last):
File "/opt/stack/
config
File "/opt/stack/
timeout=
File "/usr/local/
return self.request('PUT', url, data=data, **kwargs)
File "/usr/local/
resp = self.send(prep, **send_kwargs)
File "/usr/local/
r = adapter.
File "/usr/local/
raise ConnectionError
ConnectionError: ('Connection aborted.', BadStatusLine(
Again, this causes the config update to fail and the router never reaches the active state.
tags: | added: akanda-appliance |
Changed in akanda: | |
milestone: | none → liberty-1 |
assignee: | nobody → Adam Gandelman (gandelman-a) |
importance: | Undecided → Medium |
Changed in akanda: | |
status: | Fix Committed → Fix Released |
Changed in akanda: | |
milestone: | liberty-1 → 7.0.0 |
Changed in astara: | |
milestone: | none → 7.0.0 |
assignee: | nobody → Adam Gandelman (gandelman-a) |
importance: | Undecided → Medium |
status: | New → Fix Released |
Fix proposed to branch: master /review. openstack. org/188596
Review: https:/