Error During Nutanix Cluster Installation on Lenovo Nodes "because dependencies not met" | Nutanix Community
Skip to main content

Hello everyone,

I am currently experiencing an issue while installing a Nutanix cluster on two Lenovo ThinkAgile HX630 V3 CN nodes, with a witness virtual machine. Below are the detailed system versions and the error messages encountered.

AOS and AHV Versions:

  • AOS:

    • 192-168-75-10: 6.8
    • J901TNBT (ThinkAgile HX630 V3 CN): 6.5.3
    • J901TNBV (ThinkAgile HX630 V3 CN): 6.5.3

  • AHV:

    • 192-168-75-10: ?
    • J901TNBT (ThinkAgile HX630 V3 CN): AHV el7.nutanix.20220304.385
    • J901TNBV (ThinkAgile HX630 V3 CN): AHV el7.nutanix.20220304.385

The installation fails at the "ImagingStepProvisionNetwork" step with an error message indicating a "Timeout (240s) in waiting for events ['provision_remote']". This seems to cause a cascade of failures in subsequent installation steps, preventing the process from completing.

I have verified the current IP addresses and potential conflicts via arp-scan, but this has not resolved the issue.

Has anyone encountered this type of issue or have any suggestions on how to resolve it ?

Thank you in advance for your help.

 

Error Message:
2024-07-14 06:52:43,838Z DEBUG Setting state of <ImagingStepProvisionNetwork(<NodeConfig(192.168.75.109) @5490>) @5510> from PENDING to RUNNING
2024-07-14 06:52:43,839Z INFO Running <ImagingStepProvisionNetwork(<NodeConfig(192.168.75.109) @5490>) @5510>
2024-07-14 06:52:46,535Z INFO rpc method <unbound method NodeManager.get_ip>, target fe80::526b:8dff:fede:4001%eth0
2024-07-14 06:52:46,535Z INFO cherrypy {}
2024-07-14 06:52:48,644Z INFO Starting arp-scan to check for conflicts
2024-07-14 06:53:00,864Z INFO Current IP usage is '192.168.75.101', '192.168.75.102', '192.168.75.103', '192.168.75.104', '192.168.75.105', '192.168.75.106', '192.168.75.107', '192.168.75.108', '192.168.75.109']
2024-07-14 06:53:02,462Z INFO IPs not reported by arp-scan but in user input: '192.168.75.104', '192.168.75.105', '192.168.75.106', '192.168.75.107', '192.168.75.101', '192.168.75.102', '192.168.75.103', '192.168.75.108', '192.168.75.109']
2024-07-14 06:53:29,680Z INFO ARP scan completed successfully
2024-07-14 06:53:29,680Z INFO Waiting for remote nodes to provision network
2024-07-14 06:57:29,701Z ERROR Exception in running <ImagingStepProvisionNetwork(<NodeConfig(192.168.75.109) @5490>) @5510>
Traceback (most recent call last):
  File "foundation/imaging_step.py", line 161, in _run
    self.run()
  File "foundation/imaging_step_provision_network.py", line 237, in run
    timeout=provision_remote_nodes_wait_time)
  File "foundation/config_manager.py", line 352, in wait_for_event
    "Timeout (%ss) in waiting for events %s" % (timeout, event_names))
EventTimeoutException: Timeout (240s) in waiting for events o'provision_remote']
2024-07-14 06:57:29,702Z DEBUG Setting state of <ImagingStepProvisionNetwork(<NodeConfig(192.168.75.109) @5490>) @5510> from RUNNING to FAILED
2024-07-14 06:57:29,703Z DEBUG Setting state of <ImagingStepValidation(<NodeConfig(192.168.75.109) @5490>) @56d0> from PENDING to NR
2024-07-14 06:57:29,703Z WARNING Skipping <ImagingStepValidation(<NodeConfig(192.168.75.109) @5490>) @56d0> because dependencies not met, failed tasks: e<ImagingStepProvisionNetwork(<NodeConfig(192.168.75.109) @5490>) @5510>]
2024-07-14 06:57:29,704Z DEBUG Setting state of <ImagingStepHandoffPrepare(<NodeConfig(192.168.75.109) @5490>) @5ed0> from PENDING to NR
2024-07-14 06:57:29,704Z WARNING Skipping <ImagingStepHandoffPrepare(<NodeConfig(192.168.75.109) @5490>) @5ed0> because dependencies not met
2024-07-14 06:57:29,705Z DEBUG Setting state of <GetNosVersion(<NodeConfig(192.168.75.109) @5490>) @ff50> from PENDING to NR
2024-07-14 06:57:29,705Z WARNING Skipping <GetNosVersion(<NodeConfig(192.168.75.109) @5490>) @ff50> because dependencies not met
2024-07-14 06:57:29,706Z DEBUG Setting state of <ImagingStepTypeDetection(<NodeConfig(192.168.75.109) @5490>) @5590> from PENDING to NR
2024-07-14 06:57:29,706Z WARNING Skipping <ImagingStepTypeDetection(<NodeConfig(192.168.75.109) @5490>) @5590> because dependencies not met
2024-07-14 06:57:29,707Z DEBUG Setting state of <ImagingStepInitCVM(<NodeConfig(192.168.75.109) @5490>) @5350> from PENDING to NR
2024-07-14 06:57:29,707Z WARNING Skipping <ImagingStepInitCVM(<NodeConfig(192.168.75.109) @5490>) @5350> because dependencies not met
2024-07-14 06:57:29,707Z DEBUG Setting state of <ImagingStepRAIDCheckPhoenix(<NodeConfig(192.168.75.109) @5490>) @0310> from PENDING to NR
2024-07-14 06:57:29,708Z WARNING Skipping <ImagingStepRAIDCheckPhoenix(<NodeConfig(192.168.75.109) @5490>) @0310> because dependencies not met
2024-07-14 06:57:29,708Z DEBUG Setting state of <ImagingStepPreInstall(<NodeConfig(192.168.75.109) @5490>) @0550> from PENDING to NR
2024-07-14 06:57:29,709Z WARNING Skipping <ImagingStepPreInstall(<NodeConfig(192.168.75.109) @5490>) @0550> because dependencies not met
2024-07-14 06:57:29,709Z DEBUG Setting state of <ImagingStepPhoenix(<NodeConfig(192.168.75.109) @5490>) @e550> from PENDING to NR
2024-07-14 06:57:29,709Z WARNING Skipping <ImagingStepPhoenix(<NodeConfig(192.168.75.109) @5490>) @e550> because dependencies not met
2024-07-14 06:57:29,710Z DEBUG Setting state of <InstallHypervisorKVM(<NodeConfig(192.168.75.109) @5490>) @ee10> from PENDING to NR
2024-07-14 06:57:29,710Z WARNING Skipping <InstallHypervisorKVM(<NodeConfig(192.168.75.109) @5490>) @ee10> because dependencies not met
2024-07-14 06:57:29,711Z DEBUG Setting state of <ImagingStepHandoff(<NodeConfig(192.168.75.109) @5490>) @ee90> from PENDING to NR
2024-07-14 06:57:29,711Z WARNING Skipping <ImagingStepHandoff(<NodeConfig(192.168.75.109) @5490>) @ee90> because dependencies not met

 

Hi,

How r u doing the foundation, using application or VM, are you connected to IMM and 10G data port?

Lenovo do not have shared IMM/data, make sure IMM and single 10Gbe is connected and reachable.

afaik Lenovo nodes are shipped with preinstalled AOS/AHV, in case that’s not the case with you here.

F>P

Hello, thank you for your response. I confirm that the network configuration is correct.

The Lenovo servers are indeed pre-configured, and when I run the installer, they can see each other, but it reports an error message stating that I only have two nodes and that my hardware is not compatible.

My reseller informed me that it is necessary in this configuration to add a Witness machine to the infrastructure. So, I downloaded the ova 6.8 file from the Nutanix website and set up this machine on one of our VMware servers. I applied the following configuration to this machine:

https://portal.nutanix.com/page/documents/details?targetId=Prism-Element-Data-Protection-Guide-v6_0:sto-metro-availability-witness-create-t.html

 

In the Foundation, I now see my two Nutanix nodes and my Witness machine, I can apply the IPs, and it works for the two nodes via the Foundation.”

Terms & Conditions