Bug 1947766

Summary:	tripleO-common healthcheck constantly spikes CPU by lsof
Product:	Red Hat OpenStack	Reporter:	Cédric Jeanneret <cjeanner>
Component:	openstack-tripleo-common	Assignee:	Cédric Jeanneret <cjeanner>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	mburns, slinaber
Target Milestone:	z7	Keywords:	Triaged, ZStream
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-11.4.1-1.20210412113429.75bd92a.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-09 20:18:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cédric Jeanneret 2021-04-09 08:08:12 UTC

First reported on Launchpad:
https://bugs.launchpad.net/tripleo/+bug/1921714

The healthcheck invoking "lsof" seem to load the server, especially when multiple containers rely on it.

The following upstream patch[1] changes how the healthcheck_port is working so that we don't rely on lsof anymore.
After multiple tests, it seems to be lighter and faster than the original one, thus preventing the CPU spikes.

Note there's still one healthcheck relying on lsof, but it's not as used as healthcheck_port (only for one nova container, and soon-to-be deprecated services such as zaqar).

This BZ is just in order to allow a clean backport downstream.


[1] https://review.opendev.org/c/openstack/tripleo-common/+/785326

Comment 20 errata-xmlrpc 2021-12-09 20:18:39 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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement 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-2021:3762