Open Stack

Thanks a lot! I am not sure about the details on the issues hit
before, it might have something to do with certain internally
available Debian native python3 packages conflicting with the ones
from buster-train-backports. I am not sure about the current state for
our environment, maybe its db schema is already the one for Train
release. Is there any way to verify (not to change anything) that, in
order to see the current state (like issuing some sql query to see
what's in place for its db schema, and issuing some dpkg command to
see what kind of openstack related packages are currently in place ..
)? I am hoping that we might already have db schema for Train release,
and we just need to upgrade some python3 packages from
buster-train-backports .. I understand that some db schema might come
from certain packages, and if those packages are not matching the ones
from buster-train-backports, then we might have to go the db-sync path
later.

Thanks,
Hai

On Sat, Sep 11, 2021 at 8:55 AM Thomas Goirand <zigo at debian.org> wrote:
>
> On 9/10/21 11:19 PM, hai wu wrote:
> > I am new to the current environment. I just asked around, and you are
> > correct: we had to use a mix of both buster-train-backports and
> > buster, because some of the packages were breaking systems scripts,
> > also there was one python-nova that caused the rabbitmq to get into an
> > endless loop...
>
> Hi,
>
> Could you be more precise please? What package is breaking what system
> scripts? I never heard of something like this... I never heard about
> what you wrote on "python-nova that caused the rabbitmq to get into an
> endless loop" either.
>
> We've been running Nova from the Train release for quite some time now,
> and we never experienced this.
>
> Also, we did have the issue you described with Nova from Rocky, but it
> went away after upgrading to Train.
>
> > Is it possible to just upgrade this package to some later package from
> > Train, which does not have this bug, in order to work around this
> > particular buggy state? we could do some tests here, we do have a test
> > system, which is built the same way, and it is suffering from the
> > exact same live migration issue ..
>
> Yes you can upgrade, but not directly from Rocky to Train, you must
> update your control plane to Stein first, do the db-sync (ie: upgrade
> your db schema), then upgrade to Train and re-do the db-sync again.
>
> In fact, we did this in production. While it took 6 hours, it worked
> well, without a single issue.
>
> BTW, it's nice that we get in touch, though I regret you didn't do it
> earlier about the other issues you described. We (the Debian OpenStack
> package maintainers) don't bite and are happy to help! :)
>
> Cheers,
>
> Thomas Goirand (zigo)
>