Add options to control creation of keystone entities and issuing db_sync

Bug #1445000 reported by Bogdan Dobrelya on 2015-04-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When several Openstack nodes is being deployed in parallel, there could be deadlocks in DB backend when trying to db_sync or create the same keystone entities in parallel. This affects all OpenStack puppet modules which create users or roles and so on in keystone or issue db_sync.

Changed in puppet-openstack:
assignee: nobody → Bogdan Dobrelya (bogdando)
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Note, this is kinda related but I believe this should be fixed for Openstack modules as well

Sanjay Upadhyay (saneax) on 2015-05-15
Changed in puppet-openstack:
status: New → Confirmed
Revision history for this message
Yanis Guenane (yanis-guenane) wrote :

For the db_sync issue, if my undstanding is correct, this serie of patches[1] aims to fix that

So if you have multiple controller nodes that does db_sync and you have a Galera (or any master/master replication setup) you basically enable the db_sync on a single node only and set it to false for the other node.


If I am totally out topic please let me know.

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Thank you for update @Yanius. This looks great and addressing the issue very well, thank you

Changed in puppet-openstack:
assignee: Bogdan Dobrelya (bogdando) → nobody
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I cannot assign the bug to you, so feel free to catch it up :)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers