fwaas has an extra db migration branch

Bug #1615578 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
YAMAMOTO Takashi

Bug Description

Ibc2df1f26407b7482cd58978c11d9a2845972ba2 introduced another db migration branch
in addition to expand and contract. it seems wrong.

Tags: fwaas
tags: added: fwaas
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-fwaas (master)

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

Changed in neutron:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: New → In Progress
Revision history for this message
Henry Gessau (gessau) wrote :

If the intent was to "start over" for v2 then this might have been a strategy. However, starting over would throw current users under the bus. Instead we should add the new v2 stuff on the existing expand branch and submit contract migrations to get current users off v1.

Also, we should block any new migrations until the model-migration sync tests are enabled.

Revision history for this message
Nate Johnston (nate-johnston) wrote :

Please verify that the merge of https://review.openstack.org/#/c/358728/ fixed your issues.

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

this is not a duplicate of 1615572.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

@Yamamoto: unfortunately LP does not have a way to link related bugs. We end up filing multiple bugs related to the same issue, and we usually end up closing only one with the end result that our LP queue keeps growing and that is very frustrating. That's why I usually mark bugs duplicated: to keep the discussion in one place and make sure we don't have bugs dangling around.

There is no harm in capturing multiple issues within the scope of a single bug report. Now this might not be the case of this bug but what closes the bug https://review.openstack.org/358913 has nothing to do with what avoided the extra branching, and that is very confusing.

Changed in neutron:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-fwaas (master)

Reviewed: https://review.openstack.org/358913
Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=84fb223ee15542204836dc8d82665773d4ee0bbe
Submitter: Jenkins
Branch: master

commit 84fb223ee15542204836dc8d82665773d4ee0bbe
Author: YAMAMOTO Takashi <email address hidden>
Date: Tue Aug 23 09:45:55 2016 +0900

    Fix db migration chain

    Closes-Bug: #1615578
    Change-Id: Idacd6b953633c9b4b34165f90db4578093cfe599

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron-fwaas (master)

Change abandoned by YAMAMOTO Takashi (<email address hidden>) on branch: master
Review: https://review.openstack.org/358541

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-fwaas 9.0.0.0b3

This issue was fixed in the openstack/neutron-fwaas 9.0.0.0b3 development milestone.

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

Other bug subscribers

Remote bug watches

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