Bug 889766

Summary: Warning message when running openstack-db -y --init --service glance --rootpw openstack
Product: Red Hat OpenStack Reporter: Gary Kotton <gkotton>
Component: openstack-glanceAssignee: Eoghan Glynn <eglynn>
Status: CLOSED ERRATA QA Contact: Attila Fazekas <afazekas>
Severity: unspecified Docs Contact:
Priority: low    
Version: 2.0 (Folsom)CC: eglynn, fpercoco
Target Milestone: snapshot2Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-glance-2012.2.1-5.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 13:24:18 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Gary Kotton 2012-12-23 07:10:41 EST
Description of problem:
Get warning message when invoking command in summary:

[root@gkotton-rhel64-1 ~]# openstack-db -y --init --service glance --rootpw openstack
Verified connectivity to MySQL.
Creating 'glance' database.
Asking openstack-glance to sync the database.
/usr/lib/python2.6/site-packages/migrate/changeset/schema.py:554: SAWarning: <type 'NoneType'> being associated with <class 'sqlalchemy.schema.Column'> object after the <class 'sqlalchemy.schema.Column'> has already been used in a SQL generation; previously generated constructs may contain stale state.
  self.table = None
/usr/lib/python2.6/site-packages/glance/db/sqlalchemy/migrate_repo/versions/003_add_disk_format.py:46: SADeprecationWarning: useexisting is deprecated.  Use extend_existing.

Version-Release number of selected component (if applicable):

How reproducible:
100% if no database exists

Steps to Reproduce:
1. Run command in summary
Actual results:

Expected results:

Additional info:
Comment 2 Eoghan Glynn 2013-01-03 10:53:10 EST
Already fixed upstream with:


These fixes, though trivial, touch the migrate_repo scripts ... however in this case, we can allow them onto stable/folsom as only *pre-existing* scripts are touched and the resulting DB is unchanged.
Comment 3 Eoghan Glynn 2013-01-25 11:53:24 EST
The first patch, https://review.openstack.org/5031, is already backported to stable/folsom.

Whereas the second patch, https://review.openstack.org/14177, was not backported at the time of landing on master.

I've addressed this oversight as:

Comment 4 Eoghan Glynn 2013-01-25 15:08:21 EST
Landed upsteam on stable/folsom:

Comment 8 errata-xmlrpc 2013-02-14 13:24:18 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.