Tempest novnc tests fail behind reverse proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Undecided
|
Oleksandr Savatieiev |
Bug Description
tempest.
https:/
This can be fixed in the nginx reverse proxy setup by adding "proxy_pass_header Server;" so that the proxied Server header is returned instead of nginx, but I would prefer to avoid that. Removing that assertion sounds like a bad idea, and I'm not sure what _validate_
tempest output:
tempest.
-------
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/Users/
File "/Users/
'Did not get the expected WebSocket HTTP Response.')
File "/Users/
raise self.failureExc
AssertionError: False is not true : Did not get the expected WebSocket HTTP Response.
Captured pythonlogging:
~~~~~~~
2018-02-08 19:50:56,460 17605 DEBUG [tempest.
2018-02-08 19:50:56,653 17605 INFO [tempest.
2018-02-08 19:50:56,653 17605 DEBUG [tempest.
Body: {"os-getVNCCons
Response - Headers: {'status': '200', u'content-length': '118', 'content-location': 'http://
Body: {"console": {"url": "http://
tcp stream dump from wireshark:
GET /websockify HTTP/1.1
Host: 10.2.0.8:6080
Upgrade: websocket
Connection: Upgrade
Cookie: token=bad6b5be1
Sec-WebSocket-Key: x3JJHMbDL1EzLkh
Sec-WebSocket-
Sec-WebSocket-
HTTP/1.1 101 Switching Protocols
Server: nginx/1.12.2
Date: Fri, 09 Feb 2018 01:40:24 GMT
Connection: upgrade
Upgrade: websocket
Sec-WebSocket-
Sec-WebSocket-
Changed in tempest: | |
assignee: | nobody → Oleksandr Savatieiev (osavatieiev) |
status: | New → In Progress |
Fix proposed: https:/ /review. openstack. org/#/c/ 557388/