Bug 1253526

Summary:	Increase the MySQL max_connections on the undercloud
Product:	Red Hat OpenStack	Reporter:	Gaëtan Trellu <gtrellu>
Component:	rhosp-director	Assignee:	chris alfonso <calfonso>
Status:	CLOSED DUPLICATE	QA Contact:	yeylon <yeylon>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Director	CC:	chlong, gchenuet, hbrock, mburns, nauvray, rhel-osp-director-maint, srevivo, vmindru
Target Milestone:	---	Keywords:	ZStream
Target Release:	Director
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-14 05:25:05 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 Gaëtan Trellu 2015-08-14 02:22:16 UTC

Description of problem:

During an Heat stack deletion, the stack failed and we are unable to remove it even after many retries.
We can see MySQL max_connection errors in the Heat logs:

   OperationalError: (_mysql_exceptions.OperationalError) (1040, 'Too many connections')\n"]."

The full log is in the "Additional info" section.

After raised the max_connections to 2048, I was able to delete the Heat stack.

Version-Release number of selected component (if applicable):

rhos-release-0.66-1.noarch
python-rdomanager-oscplugin-0.0.8-44.el7ost.noarch
puddle images 2015-07-30.1

How reproducible:

It can be reproduce with big Heat stack, like 10 nodes to deploy.

Steps to Reproduce:
1. Heat stack deployment
2. Heat stack deletion

Actual results:

Unable to delete the Heat stack even after many retries.

Expected results:

Be able to delete an Heat stack without error.

Additional info:

Heat error logs: http://pastebin.test.redhat.com/305355

Comment 3 Mike Burns 2015-08-14 05:25:05 UTC


*** This bug has been marked as a duplicate of bug 1243600 ***