| Summary: | sqlalchemy-migrate warnings during nova install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark McLoughlin <markmc> |
| Component: | openstack-nova | Assignee: | Mark McLoughlin <markmc> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | alexander.sakhnov, asalkeld, markmc, matt_domsch, micadeyeye, mlvov, pasteur, pbrady, p, rkukura |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-08 08:45:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Mark McLoughlin
2011-10-20 06:39:40 UTC
And what's the fix for this bug? I can't continue installation because of it. [micadeyeye@micadeyeye ~]$ sudo openstack-nova-db-setup . . . Asking openstack-nova to sync the databse. /usr/lib/python2.7/site-packages/migrate/changeset/schema.py:551: 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.7/site-packages/migrate/changeset/schema.py:124: MigrateDeprecationWarning: Passing a Column object to alter_column is deprecated. Just pass in keyword parameters instead. MigrateDeprecationWarning Complete! I vaguely remember getting that _warning_ too. However everything subsequently worked fine. Yeah, the warning shouldn't be causing openstack-nova-db-setup to fail Michael - are you sure the script failed? *** Bug 796350 has been marked as a duplicate of this bug. *** Ok, looks like we won't get around to fixing this on Fedora 16 but it's not an issue on Fedora 17 |