Bug 1691581 - [OSP 13] nova-novncproxy does not handle TCP RST cleanly when using SSL
Summary: [OSP 13] nova-novncproxy does not handle TCP RST cleanly when using SSL
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: melanie witt
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On: 1691580 1693821
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-22 00:39 UTC by Joshua Padman
Modified: 2023-03-21 19:15 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1691580
Environment:
Last Closed: 2019-04-26 22:23:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-23429 0 None None None 2023-03-21 19:15:53 UTC

Description Joshua Padman 2019-03-22 00:39:34 UTC 
+++ This bug was initially created as a clone of Bug #1691580 +++

The following is paraphrased from the upstream bug report.
https://bugs.launchpad.net/nova/+bug/1816727/

This should be considered a security hardening bug as it could lead to a denial of service situation. It has been determined the same upstream.

Description of problem (nova-novncproxy):
With haproxy acting as a load balancer, but not terminating SSL. 

With that health check enabled, it was found the nova-novncproxy process CPU spiking and eventually causing the node to hang. 

It seems that the haproxy health checks initiate an SSL connection but then immediately send a TCP RST.

For most services this does not seem to be an issue, but for nova-novncproxy it repeatedly initializes NovaProxyRequestHandler which creates a full nova.compute.rpcapi.ComputeAPI instance which very quickly starts to consume significant CPU and overtake the host.
Comment 1 melanie witt 2019-04-26 22:23:37 UTC 
This bug does not exist in nova version <= queens.
Note You need to log in before you can comment on or make changes to this bug.