Comment 12 for bug 1928383

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

I've done some more investigations (these are notes to help think it through). After an HA installation, the following settings are available on the 3 cinder units:

cinder/2 is the leader

root@juju-81f31a-zaza-ba0026754297-13:/var/lib/juju/agents/unit-cinder-2/charm# relation-get -r cluster:0 - cinder/0
cinder-db-initialised-echo: cinder/2-5acabdb0-dd12-46a7-a792-5a283b88fd48

root@juju-81f31a-zaza-ba0026754297-13:/var/lib/juju/agents/unit-cinder-2/charm# relation-get -r cluster:0 - cinder/1
admin-address: 172.20.1.70
cinder-db-initialised-echo: cinder/2-5acabdb0-dd12-46a7-a792-5a283b88fd48

root@juju-81f31a-zaza-ba0026754297-13:/var/lib/juju/agents/unit-cinder-2/charm# relation-get -r cluster:0 - cinder/2
admin-address: 172.20.1.157
cinder-db-initialised: cinder/2-5acabdb0-dd12-46a7-a792-5a283b88fd48

Notice that on cinder/2 (the master) there is *no* -echo key set, whereas on the non-leader units the -echo key is set (which is expected). The only unit that sets cinder-db-initialised is the leader (again expected).