Search Engine: Elastic

Article ID: 129605, created on Oct 11, 2016, last review on Oct 11, 2016

  • Applies to:
  • Operations Automation 6.0


Customer decided to change front net IP address on the VZ node. The IP was changed by the following steps:

  1. Remove all VEs from host.
  2. Remove VZ host from OSA
  3. Change IP address on VZ host
  4. Register host with new IPs.

After re-registering host all provisioning operation fail with message "Cannot find suitable hardware node".

The following error could be seen in /var/log/IM/PACI-im.log on IM host:

DEBUG chooseHnAndNewSubnet [Grizzly(3)] - ==>  Preparing: SELECT * FROM list_suitable_nodes(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
DEBUG chooseHnAndNewSubnet [Grizzly(3)] - ==> Parameters: DEFAULT(String), 11(Integer), 1(Integer), 1000(Integer), 1024(Integer), 0(Integer), 50(Integer), 100(Integer), 1(Integer), 0(Integer), 100(Integer)
DEBUG chooseHnAndNewSubnet [Grizzly(3)] - <==      Total: 0
DEBUG EventHelper [Grizzly(3)] - P30002: Cannot find suitable hardware node


Virtuozzo storage ID is not set for corresponding Virtualization Node.


  1. Navigate to PCP>Services>Cloud Infrastructure>Virtualization Nodes>Virtualization Node Name>Cloud
  2. Click "Mark as not ready to provide".
  3. Click Configure.
  4. Click the following option under: Configure Virtuozzo storage for the virtualization node
    • Allow this node to use Virtuozzo storage cluster
  5. Click Save.
  6. Click "Mark as ready to provide".
  7. Restart failed provisioning task.

Following values will be added automatically after above steps:

Virtuozzo storage ID 
Virtuozzo storage Capacity

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF