Bug 1721557 - mysql process consuming 400% CPU
Summary: mysql process consuming 400% CPU
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z4
: 14.0 (Rocky)
Assignee: Pradeep Kilambi
QA Contact: Nataf Sharabi
URL:
Whiteboard:
Depends On: 1709075 1721647
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-18 14:39 UTC by Vinay Kapalavai
Modified: 2019-11-06 16:48 UTC (History)
16 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.3.1-0.20190513171739.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1709075
Environment:
Last Closed: 2019-11-06 16:47:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3745 0 None None None 2019-11-06 16:48:32 UTC

Comment 6 Lon Hohberger 2019-09-04 10:44:22 UTC
According to our records, this should be resolved by openstack-tripleo-heat-templates-9.3.1-0.20190513171752.el7ost.  This build is available now.

Comment 8 Leonid Natapov 2019-10-27 13:20:34 UTC
openstack-tripleo-heat-templates-9.3.1-0.20190513171765.el7ost.noarch

[root@controller-1 heat-admin]# docker ps --filter name=_cron --format "{{.Names}}"
panko_api_cron
heat_api_cron
cinder_api_cron
logrotate_crond
nova_api_cron
keystone_cron

[root@controller-1 heat-admin]# docker ps | grep panko
779761334f12        192.168.24.1:8787/rhosp14/openstack-panko-api:2019-10-03.1                    "kolla_start"            5 days ago          Up 5 days (healthy)                       panko_api
50c5e97b9152        192.168.24.1:8787/rhosp14/openstack-panko-api:2019-10-03.1                    "kolla_start"            5 days ago          Up 5 days                                 panko_api_cron

We have panko_api_cron container healthy and running.

Comment 10 errata-xmlrpc 2019-11-06 16:47:53 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-2019:3745


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