yahoo-eng-team team mailing list archive

[Brant Knudson <bknudson@xxxxxxxxxx>]

Public bug reported:

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_dbi::ProgrammingError: Statement Execute
Failed: [IBM][CLI Driver][DB2/LINUXX8664] SQL0205N  Column, attribute,
or period "REQUESTED_ROLES" is not defined in "KEYSTONE.REQUEST_TOKEN".
SQLSTATE=42703 SQLCODE=-205 '\nALTER TABLE request_token ALTER COLUMN
requested_roles DROP NOT NULL' ()

So it's saying the column doesn't exist for the alter table when making
the column nullable.

Here's the code:

    request_token_table.c.requested_roles.alter(name="role_ids",
nullable=True)

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.

** Affects: keystone
     Importance: Undecided
     Assignee: Brant Knudson (blk-u)
         Status: In Progress

** Changed in: keystone
     Assignee: (unassigned) => Brant Knudson (blk-u)

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

Title:
  db_sync with oauth1 extension fails

Status in OpenStack Identity (Keystone):
  In Progress

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_dbi::ProgrammingError: Statement Execute
  Failed: [IBM][CLI Driver][DB2/LINUXX8664] SQL0205N  Column, attribute,
  or period "REQUESTED_ROLES" is not defined in
  "KEYSTONE.REQUEST_TOKEN".  SQLSTATE=42703 SQLCODE=-205 '\nALTER TABLE
  request_token ALTER COLUMN requested_roles DROP NOT NULL' ()

  So it's saying the column doesn't exist for the alter table when
  making the column nullable.

  Here's the code:

      request_token_table.c.requested_roles.alter(name="role_ids",
  nullable=True)

  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.

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