okay. I'll reset it and try again.
@Moustafa Hindawi In Foundation 4.6.3 version, BMC Reset was performed, but if the same phrase appears, it does not proceed, In Foundation version 5.3.4, the image is uploaded and recognized, and installation proceeds. After rebooting, there is no response, so it falls to Fail. Up to version 5.15, the installation works fine. Is there any other method besides the BMC Reset method?
Hello @Moustafa Hindawi
Do a factory reset, Even the password is initialized, so after resetting, I try to install again with Foundation 4.6.3, but the same log is output.
2023-03-13 08:44:36,453Z INFO Did not receive expected result "Device 2 :VM Plug-In OK!!"; instead received vmwa dev2iso /home/nutanix/foundation/tmp/sessions/20230313-013532-4/phoenix_node_isos/foundation.node_11.11.11.121.iso Mounting ISO file: /home/nutanix/foundation/tmp/sessions/20230313-013532-4/phoenix_node_isos/foundation.node_11.11.11.121.iso
Device 2 :The Length of Name is not correct
Let's try another way.
Try to do Foundation using the last Foundation version, and please share the errors
When installed with Foundation 5.3.4 version, it seems to proceed normally,
but after rebooting, it waits for a very long time and then fails. If you check the log,
it seems that the problem may be that the driver error message related to the Linux 6 version appears.
Share content.
2023-03-13 07:40:23,308Z INFO Fetching driver spec for the node using the cmd: /usr/bin/python /mnt/arizona/drivers/bin/find_driver_spec.py SMIPMI kvm --hyp_distro=el6
2023-03-13 07:40:23,350Z ERROR Drivers are not available for kvm distro el6
2023-03-13 07:40:23,356Z INFO Copying network configuration crashcart scripts into /mnt/stage/root/nutanix-network-crashcart
2023-03-13 07:40:23,377Z INFO Installing firstboot marker file
2023-03-13 07:40:23,384Z INFO Setting up logrotator and creating symbolic link for cvm console log
2023-03-13 07:40:23,390Z INFO Cleaning up
2023-03-13 07:40:47,154Z INFO LVM volume group ahv was not detected; assuming that AHV is installed on normal partitions
2023-03-13 07:40:47,183Z INFO Imaging thread 'hypervisor' has completed successfully
2023-03-13 07:40:47,372Z INFO LVM volume group ahv was not detected; assuming that AHV is installed on normal partitions
2023-03-13 07:40:47,542Z INFO LVM volume group ahv was not detected; assuming that AHV is installed on normal partitions
2023-03-13 07:40:52,753Z INFO LVM volume group ahv was not detected; assuming that AHV is installed on normal partitions
2023-03-13 07:41:48,489Z INFO Imaging process completed successfully!
2023-03-13 07:41:48,505Z INFO Installation of Acropolis base software successful: Installation successful.
2023-03-13 07:41:48,512Z INFO Rebooting node. This may take several minutes: Rebooting node. This may take several minutes
2023-03-13 07:41:48,983Z INFO Rebooting node. This may take several minutes
2023-03-13 08:33:58,057Z ERROR Exception in <ImagingStepPhoenix(<NodeConfig(11.11.11.121) @1450>) @0790>
Traceback (most recent call last):
File "foundation/decorators.py", line 78, in wrap_method
File "foundation/imaging_step_phoenix.py", line 589, in run
File "foundation/imaging_step.py", line 353, in wait_for_event
StandardError: Received "fatal" in waiting for event "Last reboot complete": Aborted from API
2023-03-13 08:33:58,065Z ERROR Exception in running <ImagingStepPhoenix(<NodeConfig(11.11.11.121) @1450>) @0790>
Traceback (most recent call last):
File "foundation/imaging_step.py", line 161, in _run
File "foundation/decorators.py", line 78, in wrap_method
File "foundation/imaging_step_phoenix.py", line 589, in run
File "foundation/imaging_step.py", line 353, in wait_for_event
StandardError: Received "fatal" in waiting for event "Last reboot complete": Aborted from API
2023-03-13 08:33:58,067Z DEBUG Setting state of <ImagingStepPhoenix(<NodeConfig(11.11.11.121) @1450>) @0790> from RUNNING to FAILED
sorry.
My guess may be different, but I'm not sure why. We are continuously testing,
but with the latest version of foundation, AOS 5.15.2 reboots and proceeds with CVM configuration normally, and installation is completed. Installation does not proceed in AOS 5.10 version.
