OpenStack Cinder Charm

  1. Series ussuri
  2. Bug #1928383
  3. Comment #16

Comment 16 for bug 1928383

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-cinder (master)

Reviewed: https://review.opendev.org/c/openstack/charm-cinder/+/841410
Committed: https://opendev.org/openstack/charm-cinder/commit/a50281db835fc139912f09fedb6e00dba9f333a5
Submitter: "Zuul (22348)"
Branch: master

commit a50281db835fc139912f09fedb6e00dba9f333a5
Author: Alex Kavanagh <email address hidden>
Date: Wed May 11 12:48:41 2022 +0100

    Stop endless cycles on openstack upgrade

    If an HA cinder deployment is upgraded twice and the leadership has
    changed, there is a potential race that can be triggered where because
    the CINDER_DB_INIT_RKEY is different on the units that have been the
    leader. This race is that when the unit tries to decide whether it has
    reflected the 'new' RKEY it sees a different one from each unit. By
    clearing the rkey, it ensures that only the relation changed event from
    the leader actually causes a restart.

    Change-Id: I712502a666f23421cc58925f10b7643e3482d861
    Closes-Bug: #1928383