Foundation issue | Nutanix Community
Skip to main content

Hello , 

I am trying to understand what is the role of SMCIPMITool , as I am abled to reach the IPMIs from the foundation VM yet not sure what is causing the failure , I am attempting to re-image AOS 6.5.6.6 on 2 nodes .

What I have found so far it is responsible to reboot , power on / off the hosts via IPMI not sure why it can not power them back on.

 

during the foundation the nodes are powered off then the below traces are seen  

Traceback (most recent call last):
  File "foundation/imaging_step.py", line 160, in _run
  File "foundation/decorators.py", line 78, in wrap_method
  File "foundation/imaging_step_init_ipmi.py", line 289, in run
  File "foundation/imaging_step_init_ipmi.py", line 129, in boot_phoenix
  File "/home/nutanix/foundation/lib/foundation-platforms/foundation_bmc-2.16+r.2114.64ba09cb-py2.py3-none-any.whl/bmc_utils/boot_media.py", line 47, in wrapped
    return fn(self, iso, *args, **kwargs)
  File "/home/nutanix/foundation/lib/foundation-platforms/foundation_bmc-2.16+r.2114.64ba09cb-py2.py3-none-any.whl/bmc_utils/_remote_boot_vmwa.py", line 200, in boot
    self.reset_bmc()
  File "/home/nutanix/foundation/lib/foundation-platforms/foundation_bmc-2.16+r.2114.64ba09cb-py2.py3-none-any.whl/bmc_utils/_remote_boot_vmwa.py", line 124, in reset_bmc
    self.new_bmc_shell()
  File "/home/nutanix/foundation/lib/foundation-platforms/foundation_bmc-2.16+r.2114.64ba09cb-py2.py3-none-any.whl/bmc_utils/_remote_boot_vmwa.py", line 254, in new_bmc_shell
    raise Exception("SMCIPMITool failed to start - giving up")
Exception: SMCIPMITool failed to start - giving up
2024-11-28 13:20:47,680Z imaging_step.py:123 DEBUG Setting state of <ImagingStepInitIPMI(<NodeConfig(x.x.x.x) @03a0>) @2820> from RUNNING to FAILED
2024-11-28 13:20:47,689Z imaging_step.py:123 DEBUG Setting state of <ImagingStepRAIDCheckPhoenix(<NodeConfig(x.x.x.x) @03a0>) @2e50> from PENDING to NR
2024-11-28 13:20:47,690Z imaging_step.py:182 WARNING Skipping <ImagingStepRAIDCheckPhoenix(<NodeConfig(x.x.x.x) @03a0>) @2e50> because dependencies not met, failed tasks: n<ImagingStepInitIPMI(<NodeConfig(x.x.x.x) @03a0>) @2820>]
2024-11-28 13:20:47,691Z imaging_step.py:123 DEBUG Setting state of <ImagingStepPreInstall(<NodeConfig(x.x.x.x) @03a0>) @c430> from PENDING to NR
2024-11-28 13:20:47,691Z imaging_step.py:182 WARNING Skipping <ImagingStepPreInstall(<NodeConfig(x.x.x.x) @03a0>) @c430> because dependencies not met
2024-11-28 13:20:47,692Z imaging_step.py:123 DEBUG Setting state of <ImagingStepPhoenix(<NodeConfig(x.x.x.x) @03a0>) @0790> from PENDING to NR
2024-11-28 13:20:47,693Z imaging_step.py:182 WARNING Skipping <ImagingStepPhoenix(<NodeConfig(x.x.x.x) @03a0>) @0790> because dependencies not met
2024-11-28 13:20:47,693Z imaging_step.py:123 DEBUG Setting state of <InstallHypervisorKVM(<NodeConfig(x.x.x.x) @03a0>) @0ac0> from PENDING to NR
2024-11-28 13:20:47,694Z imaging_step.py:182 WARNING Skipping <InstallHypervisorKVM(<NodeConfig(x.x.x.x) @03a0>) @0ac0> because dependencies not met
You have reached the end of this log. This deployment is no longer in progress.

​@AdelMarei Hi, try to follow this guide https://portal.nutanix.com/page/documents/kbs/details?targetId=kA07V000000LX24SAG 

I know that is a different error, but sometimes de DNS is responsible for several things. always get configured the reverse resolution as well. 

Reply


Terms & Conditions