[Bug 1094921] Re: keystone postinst fails with KeyError: <VerNum(4)>

[Adam Gandelman]

Looks like an issue in the postinst's call to 'keystone-manage db_sync'.
Can't seem to reproduce when upgrading between the same versions, using
the default (empty) local sqlite db, but this was probably hit against a
live, remote database?

James, what db backend is in use?  Can you confirm the database is under
python-migrate's version control?  There should be a 'migrate_version'
table in Keystone's database with a 'version' field, likely set to '4'
(for Essex, anyway)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1094921

Title:
  keystone postinst fails with KeyError: <VerNum(4)>

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