Search Engine: Elastic

Article ID: 118299, created on Oct 30, 2013, last review on Apr 30, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5
  • Odin Business Automation Standard 4.2
  • Odin Business Automation Standard 4.1


One of the Virtuozzo Node was physically broken and replaced with the new node. But the old node is still on the OBAS and I can't delete it with the error below:

Cannot delete the Hardware Node. There are Container(s) hosted on this Hardware Node. You can migrate Container(s) to another Hardware Node(s) and try again.


Virtuozzo HW Node cannot be deleted from OBAS because there are several containers from it registered in OBAS. In order to delete the node it's needed to delete the containers first.

Since the Virtuozzo node is not available and OBAS cannot connect to it, all the containers exist in Conflict Resolver. Please login to OBAS as provider and change to the page:

Top > Migration Director > Conflicts Resolver > Containers

Find the containers which are assigned to broken Virtuozzo Node - such containers likely have status "Container was not found on the node". Click the link and choose "Remove the information about this Container from the Parallels Business Automation - Standard database (recommended)".

This will delete the container from OBAS database automatically.

All subscriptions assigned to the containers should be terminated:

Top > Account Director > Subscription Manager > Subscriptions > *Subscription ID* > Terminate

Remember to confirm subscription termination through

Top > Account Director > Subscription Manager > Subscriptions > Termination Queue > *Subscription ID* > Destroy

Choose rule "Keep target system" on the Termination confirmation page.

After all records about the containers are removed, you'll be able to remove the broken Virtuozzo Node usual way:

Top > Service Director > Virtuozzo Manager > Nodes > *Virtuozzo node* > General Settings > Delete

caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e 93123df14254afe4bfd02eb6096092cd 62a72d260afd42b853c9105003928212 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF