Hello Anirudh, This is not the correct mailing list for Kolla nor Kolla Ansible. The correct is: openstack-discuss@lists.openstack.org Please retry there. As for your question, the observed behaviour should not be happening. Perhaps the VM was under resource pressure and got killed? Anyway, please restart this thread on the proper mailing list. Kind regards, -yoctozepto On Wed, Jul 14, 2021 at 3:31 PM Anirudh Gupta <anyrude10@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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss