Bug 1321819 - Unable to delete test DB while deploying overcloud at Step4
Summary: Unable to delete test DB while deploying overcloud at Step4
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-29 08:30 UTC by Qasim Sarfraz
Modified: 2016-11-14 12:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-14 12:09:13 UTC
Target Upstream Version:


Attachments (Terms of Use)
Mysql logs (169.43 KB, application/x-gzip)
2016-03-29 08:30 UTC, Qasim Sarfraz
no flags Details

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.


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