db-migration: we run cleanup of cache keys AFTER upgrade.
- this allows actually migrating CacheKeys - this step is optional, and it it fails it's not the end of the world, we still would run migration anyway.
This commit is contained in:
parent
37991ffd4e
commit
b018a07f93
1 changed files with 2 additions and 2 deletions
|
|
@ -117,7 +117,7 @@ class DbManage(object):
|
|||
self.sa.add(ver)
|
||||
log.info('db version set to: %s', __dbversion__)
|
||||
|
||||
def run_pre_migration_tasks(self):
|
||||
def run_post_migration_tasks(self):
|
||||
"""
|
||||
Run various tasks before actually doing migrations
|
||||
"""
|
||||
|
|
@ -172,7 +172,6 @@ class DbManage(object):
|
|||
|
||||
notify(msg)
|
||||
|
||||
self.run_pre_migration_tasks()
|
||||
|
||||
if curr_version == __dbversion__:
|
||||
log.info('This database is already at the newest version')
|
||||
|
|
@ -194,6 +193,7 @@ class DbManage(object):
|
|||
|
||||
_step = step
|
||||
|
||||
self.run_post_migration_tasks()
|
||||
notify('upgrade to version %s successful' % _step)
|
||||
|
||||
def fix_repo_paths(self):
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue