Valid column creation in token table fails with postgres
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dirk Mueller |
Bug Description
When migrating from the Essex to the Folsom version of Ubuntu 12.04 with postgres I get the following error when keystone tries to update the database schema.
For it to work, I needed to truncate the token table in the keystone database. If this is better posted with the Ubuntu package maintainer, please let me know.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up keystone (2012.2-
Traceback (most recent call last):
File "/usr/bin/
cli.
File "/usr/lib/
return run(cmd, (args[:1] + args[2:]))
File "/usr/lib/
return CMDS[cmd]
File "/usr/lib/
return self.main()
File "/usr/lib/
driver.
File "/usr/lib/
migration.
File "/usr/lib/
return versioning_
File "/usr/lib/
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
File "<string>", line 2, in _migrate
File "/usr/lib/
return f(*a, **kw)
File "/usr/lib/
schema.
File "/usr/lib/
change.
File "/usr/lib/
script_
File "/usr/lib/
token.
File "/usr/lib/
column.
File "/usr/lib/
engine.
File "/usr/lib/
conn.
File "/usr/lib/
**kwargs)
File "/usr/lib/
ret = super(AlterTabl
File "/usr/lib/
return meth(obj, **kw)
File "/usr/lib/
self.execute()
File "/usr/lib/
return self.connection
File "/usr/lib/
params)
File "/usr/lib/
statement, parameters
File "/usr/lib/
context)
File "/usr/lib/
context)
File "/usr/lib/
cursor.
sqlalchemy.
'\nALTER TABLE token ADD valid BOOLEAN NOT NULL' {}
dpkg: error processing keystone (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
keystone
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@ha3:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up keystone (2012.2-
Traceback (most recent call last):
File "/usr/bin/
cli.
File "/usr/lib/
return run(cmd, (args[:1] + args[2:]))
File "/usr/lib/
return CMDS[cmd]
File "/usr/lib/
return self.main()
File "/usr/lib/
driver.
File "/usr/lib/
migration.
File "/usr/lib/
return versioning_
File "/usr/lib/
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
File "<string>", line 2, in _migrate
File "/usr/lib/
return f(*a, **kw)
File "/usr/lib/
schema.
File "/usr/lib/
change.
File "/usr/lib/
script_
File "/usr/lib/
token.
File "/usr/lib/
column.
File "/usr/lib/
engine.
File "/usr/lib/
conn.
File "/usr/lib/
**kwargs)
File "/usr/lib/
ret = super(AlterTabl
File "/usr/lib/
return meth(obj, **kw)
File "/usr/lib/
self.execute()
File "/usr/lib/
return self.connection
File "/usr/lib/
params)
File "/usr/lib/
statement, parameters
File "/usr/lib/
context)
File "/usr/lib/
context)
File "/usr/lib/
cursor.
sqlalchemy.
'\nALTER TABLE token ADD valid BOOLEAN NOT NULL' {}
dpkg: error processing keystone (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
Changed in keystone: | |
assignee: | Adam Young (ayoung) → Dirk Mueller (dmllr) |
status: | Triaged → In Progress |
Changed in keystone: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | grizzly-3 → 2013.1 |
Adam,
Do you have a postgres database setup for Keystone? I recall you talking about wanting to move Postgres to a first-class citizen at the summit. It looks like something we've got in one of the migration scripts isn't happy on that system in particular.