Open Stack

Hi Radosław

Thanks for your reply.
Is there any configuration or anything workaround avoid this?

Regards
Anirudh Gupta

On Sat, 17 Jul, 2021, 12:27 am Radosław Piliszek, <
radoslaw.piliszek at gmail.com> wrote:

> For the record, in the other mailing thread (on stx) I suggested this
> should not be happening and it was likely some resource pressure.
>
> -yoctozepto
>
> On Fri, Jul 16, 2021 at 8:31 PM Anirudh Gupta <anyrude10 at gmail.com> wrote:
> >
> > Hi Team,
> >
> > We have deployed the Openstack Victoria release using Multinode Kolla
> Ansible deployment.
> >  There are 2 nodes - one for compute and other for Controller+Network
> >
> > Following the below link, we also upgraded the setup from Victoria to
> wallaby
> >
> >
> https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html
> >
> > During the Upgrade process, we figured out that the VM which was spawned
> before Upgrade went to shut off during the middle of Upgrade process and
> post completion of the upgrade process, we had to manually start the VM
> again.
> >
> > Ideally we were expecting that the existing Workloads would remain
> unimpacted in this process.
> >
> > Can someone please suggest if our observation is correct or any steps
> that needs to be taken in order to avoid this?
> >
> > Regards
> > Anirudh Gupta
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210717/dff5520e/attachment.html>