primary controller database resyncs at the end of the cluster formation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Alex Schultz | ||
Mitaka |
Fix Released
|
Medium
|
Alex Schultz |
Bug Description
Detailed bug description:
Durring galera cluster formation, the primary-controller database is being restarted after the other databases join the cluster. This shows up as a keystone db task failure because the mysql instance may restart while being written to causing a task failure.
Please see all info at https:/
Steps to reproduce:
1. Create cluster with Neutron
2. Add 3 nodes with controller role
3. Add 3 nodes with compute and ceph-osd role
4. Deploy the cluster
....
Expected results:
Deployment will be successful
Actual result:
Failed tasks: Task[primary-
(/Stage[
Failed to call refresh: keystone-manage db_sync returned 1 instead of one of [0]
Description of the environment:
See link above
tags: | removed: swarm-blocker |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Maksim Malchuk (mmalchuk) |
tags: | added: on-verification |
Raising to critical as it is BVT blocker