yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #28511
[Bug 1422315] [NEW] novncproxy fails to establish a VNC connection, if a reverse DNS look up times out
Public bug reported:
If DNS is configured on a node in a way, so that reverse DNS look ups
time out, noVNC will fail to connect to an instance with 'Connect
timeout' error.
The reverse DNS look up is done implicitly in BaseHTTPRequestHandler
(part of standard library), when logging a request. It's not
configurable, so the only way to disable it is to override the method
of the base class (https://github.com/python/cpython/blob/2.6/Lib/BaseHTTPServer.py#L487).
This is only true for the standard http server (used for novncproxy),
as the eventlet implementation (used for xvpvncproxy) seems to use
plain IP addresses without any reverse DNS look ups.
** Affects: nova
Importance: Undecided
Assignee: Roman Podoliaka (rpodolyaka)
Status: In Progress
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Roman Podoliaka (rpodolyaka)
** Summary changed:
- novncproxy fails to establish a VNC connection, if reverse DNS loop up times out
+ novncproxy fails to establish a VNC connection, if a reverse DNS look up times out
--
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/1422315
Title:
novncproxy fails to establish a VNC connection, if a reverse DNS look
up times out
Status in OpenStack Compute (Nova):
In Progress
Bug description:
If DNS is configured on a node in a way, so that reverse DNS look ups
time out, noVNC will fail to connect to an instance with 'Connect
timeout' error.
The reverse DNS look up is done implicitly in BaseHTTPRequestHandler
(part of standard library), when logging a request. It's not
configurable, so the only way to disable it is to override the method
of the base class (https://github.com/python/cpython/blob/2.6/Lib/BaseHTTPServer.py#L487).
This is only true for the standard http server (used for novncproxy),
as the eventlet implementation (used for xvpvncproxy) seems to use
plain IP addresses without any reverse DNS look ups.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1422315/+subscriptions
Follow ups
References