← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1292591] Re: Database models differs from migrations.

 

I'm assuming this was fixed by the last patch. In the future, please use
Closes-Bug on the final patch in your patch sequence -- not just
Partial-Bug on all of them (which leaves the bug open).

** Changed in: keystone
       Status: In Progress => Fix Committed

** Changed in: keystone
    Milestone: None => 2015.1.0

** Changed in: keystone
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1292591

Title:
  Database models differs from migrations.

Status in Keystone:
  Fix Released

Bug description:
  As models and migrations don't have any logical relation in code, so
  differences are possible. Furthermore in most of cases differences
  exists. The only way to solve this problem is using of specific test
  such as this https://review.openstack.org/#/c/74081/  .

  This is a diff example form Keystone:

  AssertionError: Models and migration scripts aren't in sync:
  [ [ ( 'modify_nullable',
        None,
        'federation_protocol',
        'mapping_id',
        { 'existing_server_default': None,
          'existing_type': VARCHAR(length=64)},
        True,
        False)],
    [ ( 'modify_nullable',
        None,
        'region',
        'description',
        { 'existing_server_default': None,
          'existing_type': VARCHAR(length=255)},
        False,
        True)],
    ( 'remove_index',
      Index(u'ix_revocation_event_revoked_at', Column(u'revoked_at', DATETIME(), table=<revocation_event>, nullable=False))),
    [ ( 'modify_nullable',
        None,
        'token',
        'valid',
        { 'existing_server_default': None,
          'existing_type': INTEGER()},
        True,
        False)]]

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1292591/+subscriptions


References