Comment 4 for bug 1371044

I'm not sure but it looks like it's not a problem. I think the situation is:

1. Each node has two roles: controller and cinder.
2. Priorities: Primary Controller (500), Controller (600) and Cinder (700).
3. Therefore, the node has been deployed as primary controller and stops since we need to deploy secondary controllers right after primary controller.
4. When the secondary controllers was deployed, all the nodes starts deploy cinder in paralled and finishes as ready.

So I think it's ok, but I believe it should be confirmed by some guy from library team.