Bug 1691585 - [OSP 15] nova-novncproxy does not handle TCP RST cleanly when using SSL
Summary: [OSP 15] nova-novncproxy does not handle TCP RST cleanly when using SSL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 15.0 (Stein)
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:43 UTC by Joshua Padman
Modified: 2023-03-21 19:15 UTC (History)
9 users (show)

Fixed In Version: openstack-nova-19.0.1-0.20190410231429.1f6bbaa.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1691580
Environment:
Last Closed: 2020-03-05 11:54:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 649374 0 None None None 2019-04-03 17:35:50 UTC
Red Hat Issue Tracker OSP-23427 0 None None None 2023-03-21 19:15:49 UTC

Description Joshua Padman 2019-03-22 00:43:26 UTC
This is likely going to be included in 15 via a regular import.

+++ 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 4 errata-xmlrpc 2020-03-05 11:54:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0711


Note You need to log in before you can comment on or make changes to this bug.