Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1626008

Summary:	High CPU usage produced by rabbitmq on controllers
Product:	Red Hat OpenStack	Reporter:	Marian Krcmarik <mkrcmari>
Component:	openstack-tripleo-heat-templates	Assignee:	John Eckersberg <jeckersb>
Status:	CLOSED ERRATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	apevec, dhill, jeckersb, lhh, mburns, michele, srevivo
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.0.1-0.20181013060890.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:52:59 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 Marian Krcmarik 2018-09-06 11:22:29 UTC

Description of problem:
It was observed on OSP14 that rabbitmq (beam.smp process) produce relatively high CPU load during OSP environment completely in idle state. Most of the time It keeps over 50% of CPU usage, peaking to 100% often on idling system.

Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.16-1.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP14 (probably even older systems)

Actual results:
Observe CPU usage on the system by tool such as top, check beam.smp processes

Additional info:
During a node reboot It was observed that pacemaker complained about High CPU usage and bundles did not start in timeout (20s), not sure how it is connected but severity of the bug may raise If it is related.

Comment 8 errata-xmlrpc 2019-01-11 11:52:59 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/RHEA-2019:0045