Open Stack

On Tue, Jan 22, 2013 at 12:50 PM, Yug Suo <suolist at gmail.com> wrote:
> Hi, all
>
> I run my openstack(stable/folsom) with devstack(stable/folsom), but when I
> run ./stack.sh, I got the following error:
>
> 2013-01-23 01:39:46 CRITICAL nova [-] There is no script for 134 version
> 2013-01-23 01:39:46 TRACE nova Traceback (most recent call last):
> 2013-01-23 01:39:46 TRACE nova   File "/opt/stack/nova/bin/nova-manage",
> line 1404, in <module>
> 2013-01-23 01:39:46 TRACE nova     main()
> 2013-01-23 01:39:46 TRACE nova   File "/opt/stack/nova/bin/nova-manage",
> line 1391, in main
> 2013-01-23 01:39:46 TRACE nova     fn(*fn_args, **fn_kwargs)
> 2013-01-23 01:39:46 TRACE nova   File "/opt/stack/nova/bin/nova-manage",
> line 760, in sync
> 2013-01-23 01:39:46 TRACE nova     return migration.db_sync(version)
> 2013-01-23 01:39:46 TRACE nova   File
> "/opt/stack/nova/nova/db/migration.py", line 32, in db_sync
> 2013-01-23 01:39:46 TRACE nova     return IMPL.db_sync(version=version)
> 2013-01-23 01:39:46 TRACE nova   File
> "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 80, in db_sync
> 2013-01-23 01:39:46 TRACE nova     return
> versioning_api.upgrade(get_engine(), repository, version)
> 2013-01-23 01:39:46 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, in
> upgrade
> 2013-01-23 01:39:46 TRACE nova     return _migrate(url, repository, version,
> upgrade=True, err=err, **opts)
> 2013-01-23 01:39:46 TRACE nova   File "<string>", line 2, in _migrate
> 2013-01-23 01:39:46 TRACE nova   File
> "/opt/stack/nova/nova/db/sqlalchemy/migration.py", line 44, in
> patched_with_engine
> 2013-01-23 01:39:46 TRACE nova     return f(*a, **kw)
> 2013-01-23 01:39:46 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 345, in
> _migrate
> 2013-01-23 01:39:46 TRACE nova     changeset = schema.changeset(version)
> 2013-01-23 01:39:46 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 80, in
> changeset
> 2013-01-23 01:39:46 TRACE nova     changeset =
> self.repository.changeset(database, start_ver, version)
> 2013-01-23 01:39:46 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/migrate/versioning/repository.py", line
> 225, in changeset
> 2013-01-23 01:39:46 TRACE nova     changes =
> [self.version(v).script(database, op) for v in versions]
> 2013-01-23 01:39:46 TRACE nova   File
> "/usr/lib/python2.7/dist-packages/migrate/versioning/version.py", line 184,
> in script
> 2013-01-23 01:39:46 TRACE nova     "There is no script for %d version" %
> self.version
> 2013-01-23 01:39:46 TRACE nova AssertionError: There is no script for 134
> version
> 2013-01-23 01:39:46 TRACE nova
>
>
> I can't find why on the internet, someone can help me ?

I have seen similar issues when downgrading from stable/folsom
to stable/essex where there were lingering .pyc files in the migration
directory. I would double check the
nova/db/sqlalchemy/migrate_repo/versions directory for any .pyc
files that do not have corresponding .py files. These are likely
newer migration scripts from master.

To fix this I usually just clean out the .pyc files in the directory
when downgrading.

HTH,
David.