Setting up database schema with db_sync fails in migration 039 (SQLITE)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Nathan Kinder | ||
keystone (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
A fresh clone of master (commit ee4ee3b7f570d44
On a fresh install of ubuntu 12.04.3 (yes, I know, but it's what I had kicking about) in a VM (Vmware), with no special config except for web proxies (excluding localhost) I followed
http://
and, once able to import keystone
http://
up to the point of running
bin/keystone-manage db_sync
this last command results in a stack trace as follows:
(.venv)
2014-09-19 06:54:16.321 12991 CRITICAL keystone [-] OperationalError: (OperationalError) database is locked u'DELETE FROM user_project_
2014-09-19 06:54:16.321 12991 TRACE keystone Traceback (most recent call last):
2014-09-19 06:54:16.321 12991 TRACE keystone File "bin/keystone-
2014-09-19 06:54:16.321 12991 TRACE keystone cli.main(
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone CONF.command.
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone migration_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone _sync_common_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone init_version=
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return versioning_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return _migrate(url, repository, version, upgrade=True, err=err, **opts)
2014-09-19 06:54:16.321 12991 TRACE keystone File "<string>", line 2, in _migrate
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return f(*a, **kw)
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone schema.
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone change.
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone script_func(engine)
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone migrate_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone migrate_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return connection.
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return meth(self, multiparams, params)
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone return connection.
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone compiled_sql, distilled_params
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone context)
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone util.raise_
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone reraise(
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone context)
2014-09-19 06:54:16.321 12991 TRACE keystone File "/home/
2014-09-19 06:54:16.321 12991 TRACE keystone cursor.
2014-09-19 06:54:16.321 12991 TRACE keystone OperationalError: (OperationalError) database is locked u'DELETE FROM user_project_
2014-09-19 06:54:16.321 12991 TRACE keystone
repeating the command gets the same result (same point of failure - 039_grant_
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
2014-09-19 07:03:16.105 13337 TRACE keystone.
An unexpected error prevented the server from fulfilling your request. (HTTP 500)
So I appear to be hosed. However, I believe I cloned about a week ago and ran the same process on another machine (laptop, xubuntu 14.04) with some success - so is this a bug that has been introduced in a recent commit?
Changed in keystone: | |
status: | New → Incomplete |
summary: |
- Setting up database schema with db_sync fails with OperationalError: - (OperationalError) database is locked u'DELETE FROM - user_project_metadata' () + Setting up database schema with db_sync fails in migration 039 (SQLITE) |
tags: | added: db sqlite |
tags: |
added: sql removed: db |
Changed in keystone: | |
milestone: | none → juno-rc1 |
tags: | added: icehouse-backport-potential |
Changed in keystone: | |
assignee: | nobody → David Stanek (dstanek) |
Changed in keystone: | |
assignee: | David Stanek (dstanek) → Nathan Kinder (nkinder) |
Changed in keystone (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-rc1 → 2014.2 |
Looks like an issue in upgrade script 39, specifically the migrate_grant_table function. Not really sure whats going on.