[Kolla] [ Kolla-Ansible] Existing Workloads getting Impacted on Upgrade

Radosław Piliszek radoslaw.piliszek at gmail.com
Fri Jul 16 18:56:59 UTC 2021


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



More information about the openstack-discuss mailing list