yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95528
[Bug 1812856] Re: DB migration code will break after 'z' release
I'm not sure when we fixed this, but we probably fixed it since we're
releasing Epoxy these days :)
** Changed in: glance
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1812856
Title:
DB migration code will break after 'z' release
Status in Glance:
Fix Released
Bug description:
According to https://governance.openstack.org/tc/reference/release-
naming.html the next release after 'z' will be 'a'. Some of our
tooling for database migrations orders the scripts alphabetically,
which seemed a great idea when we did it back in Ocata, but is looking
problematic as we approach the end of the alphabet.
Specifically, I'm thinking of
glance/db/sqlalchemy/alembic_migrations/data_migrations/__init__.py
but there may be other places in the code.
I have no idea what's the best approach to fix this, just wanted to
file the bug so we remember to do something about it during (or
before) the Z cycle.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1812856/+subscriptions
References