Race condition to bootstrap Grafana DB
Bug #1888681 reported by
Doug Szumski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Low
|
Doug Szumski | ||
Stein |
New
|
Low
|
Unassigned | ||
Train |
Fix Released
|
Low
|
Mark Goddard | ||
Ussuri |
Fix Released
|
Low
|
Mark Goddard | ||
Victoria |
Fix Released
|
Low
|
Doug Szumski |
Bug Description
On a multi-instance Grafana deployment all nodes attempt to bootstrap the DB, one of them wins and the others either don't notice because it's already been done, or fail trying to bootstrap the DB after it's already been done. Observed in CI with Monasca Grafana (based on 4.2) but also reported on vanilla Grafana (6). Low impact to users since the containers should just restart and carry on as normal once the DB is bootstrapped.
Changed in kolla-ansible: | |
importance: | Undecided → Low |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/742688
Review: https:/