db vs migration mismatch

Bug #1607909 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tap-as-a-service
Fix Released
Undecided
YAMAMOTO Takashi

Bug Description

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/opt/stack/networking-midonet/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py", line 618, in test_models_sync
        "Models and migration scripts aren't in sync:\n%s" % msg)
      File "/opt/stack/networking-midonet/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py", line 690, in fail
        raise self.failureException(msg)
    AssertionError: Models and migration scripts aren't in sync:
    [ [ ( 'modify_nullable',
          None, 'tap_flows',
          'direction', { 'existing_server_default': False,
            'existing_type': ENUM(u'IN', u'OUT', u'BOTH')}, False,
          True)], ( 'add_index',
        Index('ix_tap_flows_tenant_id', Column('tenant_id', String(length=255), table=<tap_flows>))),
      ( 'add_index',
        Index('ix_tap_services_tenant_id', Column('tenant_id', String(length=255)
, table=<tap_services>)))]

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :
Changed in tap-as-a-service:
assignee: nobody → YAMAMOTO Takashi (yamamoto)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tap-as-a-service (master)

Reviewed: https://review.openstack.org/349012
Committed: https://git.openstack.org/cgit/openstack/tap-as-a-service/commit/?id=0b33b4e35a850bb8563d329f908a3ec5da94bf4e
Submitter: Jenkins
Branch: master

commit 0b33b4e35a850bb8563d329f908a3ec5da94bf4e
Author: YAMAMOTO Takashi <email address hidden>
Date: Sat Jul 30 03:33:09 2016 +0900

    Fix a few db vs migration mismatch

    Closes-Bug: #1607909
    Change-Id: I6f3fcca1c7e2e3bdb4fb195a058e526324b6f717

Changed in tap-as-a-service:
status: In Progress → Fix Released
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.