I'm not sure what the default http response timeout is for apache or uwsgi, but keep in mind that the default rpc_response_timeout is 60 seconds, so if we wait for the MessagingTimeout to handle this, we might have already timed out the response to the actual client.
https://stackoverflow.com/questions/24127601/uwsgi-request-timeout-in- python ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => Low ** Also affects: nova/pike Importance: Undecided Status: New ** Changed in: nova/pike Status: New => Confirmed ** Changed in: nova/pike Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1735329 Title: console-log return 500 if n-cpu is shutdown Status in OpenStack Compute (nova): Triaged Status in OpenStack Compute (nova) pike series: Confirmed Bug description: Description =========== If a compute host fails (i.e. the n-cpu process is down), request console-log will fail with 500 Steps to reproduce ================== $ sudo systemctl stop devstack@n-cpu $ nova console-log test2 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. <class 'oslo_messaging.exceptions.MessagingTimeout'> (HTTP 500) (Request-ID: req-e29f2aa4-1cf2-4db9-b327-f5a3ef6d7f6f) Expected result =============== Nova should response 4xx Actual result ============= Nova responded 500 Environment =========== 1. Exact version of OpenStack you are running. Devstack 2. Which hypervisor did you use? Libvirt + KVM 2. Which storage type did you use? LVM 3. Which networking type did you use? OVS To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1735329/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
