yahoo-eng-team team mailing list archive

[Jamie Lennox <jamielennox@xxxxxxxxxx>]

Public bug reported:

When using sqlalchemy 0.7.10 running migration
043_fixup_region_description.py fails with the error:

Traceback (most recent call last):
  File "keystone/tests/test_sql_upgrade.py", line 2546, in test_upgrade_region_unique_description
    self.upgrade(43)
  File "keystone/tests/test_sql_upgrade.py", line 139, in upgrade
    self._migrate(*args, **kwargs)
  File "keystone/tests/test_sql_upgrade.py", line 156, in _migrate
    self.schema.runchange(ver, change, changeset.step)
  File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/migrate/versioning/schema.py", line 91, in runchange
    change.run(self.engine, step)
  File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/migrate/versioning/script/py.py", line 145, in run
    script_func(engine)
  File "/home/jamie/work/keystone/keystone/common/sql/migrate_repo/versions/043_fixup_region_description.py", line 78, in upgrade
    region_table = sql.Table(_REGION_TABLE_NAME, meta, autoload=True)
  File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/sqlalchemy/util/_collections.py", line 106, in __getattr__
    raise AttributeError(key)
AttributeError: values

Upgrading to sqlalchemy 0.8.5 fixes the error, however our
requirements.txt file lists: SQLAlchemy>=0.7.8,<=0.8.99 so this should
still be valid.

I can't quite tell when the values() function was added, i assume it was
0.8 but i'm not familiar with the migration to know exactly what is
being accomplished there.

** Affects: keystone
     Importance: Undecided
         Status: New

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

Title:
  Migrate 43 fails on old sqlalchemy

Status in OpenStack Identity (Keystone):
  New

Bug description:
  When using sqlalchemy 0.7.10 running migration
  043_fixup_region_description.py fails with the error:

  Traceback (most recent call last):
    File "keystone/tests/test_sql_upgrade.py", line 2546, in test_upgrade_region_unique_description
      self.upgrade(43)
    File "keystone/tests/test_sql_upgrade.py", line 139, in upgrade
      self._migrate(*args, **kwargs)
    File "keystone/tests/test_sql_upgrade.py", line 156, in _migrate
      self.schema.runchange(ver, change, changeset.step)
    File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/migrate/versioning/schema.py", line 91, in runchange
      change.run(self.engine, step)
    File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/migrate/versioning/script/py.py", line 145, in run
      script_func(engine)
    File "/home/jamie/work/keystone/keystone/common/sql/migrate_repo/versions/043_fixup_region_description.py", line 78, in upgrade
      region_table = sql.Table(_REGION_TABLE_NAME, meta, autoload=True)
    File "/home/jamie/.virtualenvs/keystone2/lib/python2.7/site-packages/sqlalchemy/util/_collections.py", line 106, in __getattr__
      raise AttributeError(key)
  AttributeError: values

  Upgrading to sqlalchemy 0.8.5 fixes the error, however our
  requirements.txt file lists: SQLAlchemy>=0.7.8,<=0.8.99 so this should
  still be valid.

  I can't quite tell when the values() function was added, i assume it
  was 0.8 but i'm not familiar with the migration to know exactly what
  is being accomplished there.

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