db_sync with oauth1 extension fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Brant Knudson |
Bug Description
When running with DB2, migration 4 for the oauth1 extension fails with an error:
2014-02-25 11:23:40.185 CRITICAL keystone [-] ProgrammingError: (ProgrammingError) ibm_db_
So it's saying the column doesn't exist for the alter table when making the column nullable.
Here's the code:
request_
It looks like what's happening is that sqlalchemy is doing the name change first and then doing the "nullable=True" change with the original name and not the new one.
Changed in keystone: | |
assignee: | nobody → Brant Knudson (blk-u) |
Changed in keystone: | |
milestone: | none → icehouse-3 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
importance: | Undecided → Medium |
Changed in keystone: | |
milestone: | icehouse-3 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/76271
Review: https:/