Search Engine: Elastic

Article ID: 133024, created on Aug 10, 2018, last review on Aug 10, 2018

  • Applies to:
  • Operations Automation 7.3

Symptoms

Containers are not starting after Hardware Node reboot. Option "Start on the Hardware Node boot" is not set.

Option ONBOOT=AUTO is set in case of Autostart: auto is set for VE:

[root@hwnode-vz7 ~]# prlctl list -i VE_UUID | grep -i autostart
Autostart: auto
[root@hwnode-vz7 ~]# grep ONBOOT /etc/vz/conf/VE_UUID.conf
ONBOOT="auto"

Cause

Logic of Virtual Environments boot was changed in Virtuozzo 7:

Earlier, all containers with "Autostart: auto" option were started after Hardware Node reboot except those that were selected to not be started on the node shutdown. With the old approach, it was possible to start extra VEs if the node had a sudden reboot.

Now all VEs with this option that were created after the last successful shutdown will not be autostarted after HW Node crash.

For now, only if both Autostart: yes and ONBOOT="yes" options are chosen, autostart after HW node sudden reboot will begin.

Resolution

There is Virtuozzo request #PSBM-87556 to improve this behavior. Please contact Virtuozzo Team for further details.

Feature request #PFR-2014 has been submitted in order to implement the possibility to set "Autostart: yes" for containers via OA while their creation. Contact your Technical Account Manager or Pooled Technical Associate Team (pta@odin.com) in order to trace the current status of #PFR-2014.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF