Article ID: 129532, created on Sep 28, 2016, last review on Sep 28, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

Container Conflict cannot be resolved because the Container OS template is not synchronized with the Hardware Node.

Resolution

As it is stated in OBAS Provider's Guide

To create Containers, OS templates and Application templates should be installed on the Management Node and synchronized with Hardware Nodes.

If we go Top > Service Director > Virtuozzo Manager > Nodes > The Container Node > OS Templates we will see that the OS template of the Container is in Registered status and is not synchronized.

Provider's Guide explains what that means:

A template status in the templates list table tells about a template availability and existence on a Hardware Node:

   * Registered. A template RPM is absent on a Management Node, but this template configuration file exists in Odin Business Automation Standard database.

   Note: A template in a Registered state cannot be synchronized with other Hardware Nodes since a template RPM is missing and a template cannot be installed. To make a template installation on Hardware Node(s) possible, a template RPM must be installed on a Management Node first. Then a template status becomes Installed and its distribution on Hardware Nodes becomes possible.

   * Installed. Both a template configuration file and a template RPM exist on a Management Node. A template can be distributed onto any of registered Hardware Nodes.
   * Synchronized. A template configuration file and a template RPM exist on a Hardware Node. A template RPM is unpacked, i.e., a template is installed on a Hardware Node.

To put it short, to successfully resolve the conflict it is required make the OS template Registered and Synchronized on the hardware node.

There are two ways to do so.

  1. Install the template manually on the node, import it as it is described in Importing Templates from Hardware Nodes and synchronize it as per instruction below:

    Note: If a template was installed on a Hardware Node manually, then Management Node knows nothing about this and keeps a template status as not synchronized. To let the Management Node know about an actual template status, go to the Service Director > Virtuozzo Manager > Nodes, and select the Hardware Node. Click on Applications or OS templates tab. Check the box next to a template name and click the Update Synchronization State button.
    
  2. Install the OS template right in OBAS interface as it is described in Installing OS Templates

After the template is Installed and synchronized with the node it will be possible to resolve the conflict.


Please note that since Odin and Virtuozzo are separate companies Odin does not create or support Virtuozzo templates, we do not know where to find them and do not provide support in cases a template installation on the Virtuozzo node with Virtuozzo commands fails. For all those matters please contact Virtuozzo Support for assistance.


Search Words

install template

resolve

OS template is not synchronized

Container conflict

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF