OpenStack Compute (nova)

nova-manage api_db sync uses the wrong version option when synchronizing the placement database

Bug #1778734 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Chris Dent

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.

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

Fix proposed to branch: master
Review: https://review.openstack.org/579200

Changed in nova:
assignee: nobody → Chris Dent (cdent)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

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 <email address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 18.0.0.0b3

This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.