Use the actual repo for the initial version check of the db version when
performing `db_sync --check`. Previously we always used the Legacy Repo
as the repo path was not populated in the `get_init_version` function.
This allowed the case where the new expand/contract/migrate repos
matched the legacy repo version number, the `db_sync --check` command
would assume that everything was properly up to date regardless of the
version for the expand/contract/migrate repositories. This was most
noticable in the case of a db not under version control.
Reviewed: https:/ /review. opendev. org/682447 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=6bb14c0ff6c 95bbce26ce8023e f621e408c111e6
Committed: https:/
Submitter: Zuul
Branch: master
commit 6bb14c0ff6c95bb ce26ce8023ef621 e408c111e6
Author: morgan fainberg <email address hidden>
Date: Mon Sep 16 11:15:25 2019 -0700
Use correct repo for initial version check
Use the actual repo for the initial version check of the db version when
performing `db_sync --check`. Previously we always used the Legacy Repo
as the repo path was not populated in the `get_init_version` function.
This allowed the case where the new expand/ contract/ migrate repos contract/ migrate repositories. This was most
matched the legacy repo version number, the `db_sync --check` command
would assume that everything was properly up to date regardless of the
version for the expand/
noticable in the case of a db not under version control.
Change-Id: Id5e6f74a5ed96f df17e2c24146689 7974aa5a218
closes-bug: #1844157