yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #73617
[Bug 1778734] Re: nova-manage api_db sync uses the wrong version option when synchronizing the placement database
Reviewed: https://review.openstack.org/579200
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dd4e9496d37f2bc27763926327d45df01fd08a05
Submitter: Zuul
Branch: master
commit dd4e9496d37f2bc27763926327d45df01fd08a05
Author: Chris Dent <cdent@xxxxxxxxxxxxx>
Date: Fri Jun 29 16:38:43 2018 +0100
Use 'version2' when syncing placement db
The original code was started before the version2 variable existed.
Somewhere along the way the change was missed in a merge. This
corrects the migration.db_sync call to use the right version.
Change-Id: I1c0c9bbd9a2595822d74d2b82e26c39b60ca1822
Closes-Bug: #1778734
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1778734
Title:
nova-manage api_db sync uses the wrong version option when
synchronizing the placement database
Status in OpenStack Compute (nova):
Fix Released
Bug description:
https://github.com/openstack/nova/blob/b992b90d73ab745b41924db9c2173f6cecb9d85e/nova/cmd/manage.py#L859
That should be using the "version2" parameter since the "version"
parameter is deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1778734/+subscriptions
References