I can confirm this is reproduced on MOS 9.0. This is what I see in haproxy logs:
http://paste.openstack.org/show/589873/
i.e. nova-api simply shows the error it gets from haproxy - 502 bad gateway. Note, that this request is served successfully from glance-api standpoint, but haproxy rejects it due to malformed header (= in header name? - http://agiletesting.blogspot.com/2014/07/troubleshooting-haproxy-502-errors.html)
I can confirm this is reproduced on MOS 9.0. This is what I see in haproxy logs:
http:// paste.openstack .org/show/ 589873/
i.e. nova-api simply shows the error it gets from haproxy - 502 bad gateway. Note, that this request is served successfully from glance-api standpoint, but haproxy rejects it due to malformed header (= in header name? - http:// agiletesting. blogspot. com/2014/ 07/troubleshoot ing-haproxy- 502-errors. html)