Bug 1321819

Summary: Unable to delete test DB while deploying overcloud at Step4
Product: Red Hat OpenStack Reporter: Qasim Sarfraz <qasims>
Component: rhosp-directorAssignee: Mike Burns <mburns>
Status: CLOSED NOTABUG QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: dbecker, jcoufal, jslagle, mburns, morazi, qasims, rhel-osp-director-maint, rhos-maint, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-14 12:09:13 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:
Attachments:
Description Flags
Mysql logs none

Description Qasim Sarfraz 2016-03-29 08:30:26 UTC
Created attachment 1141136 [details]
Mysql logs

Description of problem:
I am trying to deploy 3 controller with pacemaker setup. But it keeps on failing at Step4 with following error messages:

r 29 02:57:56 localhost os-collect-config: #033[1;31mError: Execution of '/usr/bin/mysql -NBe drop database if exists `test`' returned 1: ERROR 1213 (40001) at line 1: Deadlock found when trying to get lock; try restarting transaction#033[0m
Mar 29 02:57:56 localhost os-collect-config: #033[1;31mError: /Stage[main]/Mysql::Server::Account_security/Mysql_database[test]/ensure: change from present to absent failed: Execution of '/usr/bin/mysql -NBe drop database if exists `test`' returned 1: ERROR 1213 (40001) at line 1: Deadlock found when trying to get lock; try restarting transaction#033[0m

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


How reproducible:
Hitting this in fresh installation with bonds configured with LACP.


Actual results:
Deployment fails at Step4.

Expected results:
Deployment should be successful.

Additional info:
Find attached logs for details.

Comment 2 Mike Burns 2016-04-07 21:36:02 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 3 James Slagle 2016-10-14 15:30:51 UTC
hi, is this still an issue for you using the latest released version?

Comment 4 Qasim Sarfraz 2016-11-14 12:09:13 UTC
Hi James, No. It seems to be fixed in the latest release we are using.

I could never understand the root cause for this. This only occurred for a leaseweb physical stack with bonded interfaces.