OpenStack Identity (keystone)

  1. Bug #1676925
  2. Comment #4

Comment 4 for bug 1676925

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

Reviewed: https://review.openstack.org/450863
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=e6ef702f22929de831f07e6f56d7b696dfa50b89
Submitter: Jenkins
Branch: master

commit e6ef702f22929de831f07e6f56d7b696dfa50b89
Author: Dolph Mathews <email address hidden>
Date: Tue Mar 28 15:40:30 2017 +0000

    Doc db_sync --expand incurring downtime in upgrades to Newton

    The current implementation of db_sync --expand automatically runs any
    outstanding legacy operations to ensure it's safety. However, that
    behavior also means that legacy migrations may violate the safety
    assumptions around --expand.

    This is only true for Mitaka to Newton upgrades, as there should not be
    any newer migrations in the legacy repository to be triggered by this
    behavior.

    [1] https://github.com/openstack/keystone/blob/0ebd557325ff16c2535dac0eb190792e6d511a79/keystone/common/sql/upgrades.py#L269-L271

    Change-Id: Ib175f7fce96011d77eb4783123cb2d265d60aa42
    Closes-Bug: 1676925