yahoo-eng-team team mailing list archive

[Brant Knudson <bknudson@xxxxxxxxxx>]

Public bug reported:


`keystone-manage db_sync` fails when you start from the 2013.2 or 2013.2.1 release.

The failure is like

 CRITICAL keystone [-] KeyError: <VerNum(35)>

The migrations for 2013.2 and 2013.2.1 end at
'034_add_default_project_id_column_to_user.py'.

The migrations for Juno start at '036_havana.py'.

The migrations for 2013.2.2 end at '036_token_drop_valid_index.py', so
migration from that release works.

The Juno migrations should be changed so that it supports going from
034.

** Affects: keystone
     Importance: Undecided
         Status: New

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

Title:
  Can't upgrade from 2013.2 or 2013.2.1 to Juno

Status in OpenStack Identity (Keystone):
  New

Bug description:
  
  `keystone-manage db_sync` fails when you start from the 2013.2 or 2013.2.1 release.

  The failure is like

   CRITICAL keystone [-] KeyError: <VerNum(35)>

  The migrations for 2013.2 and 2013.2.1 end at
  '034_add_default_project_id_column_to_user.py'.

  The migrations for Juno start at '036_havana.py'.

  The migrations for 2013.2.2 end at '036_token_drop_valid_index.py', so
  migration from that release works.

  The Juno migrations should be changed so that it supports going from
  034.

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