Red Hat Bugzilla – Bug 889766
Warning message when running openstack-db -y --init --service glance --rootpw openstack
Last modified: 2016-04-26 22:00:07 EDT
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):
100% if no database exists
Steps to Reproduce:
1. Run command in summary
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.
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:
Landed upsteam on stable/folsom:
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.