One Click Prism Central Deployment is Failing because of timeout | Nutanix Community
Skip to main content

Hi Team

I am trying to setup Prism Central in Nutanix CE. I have configured the required details in Prism Console for deploying prism central. My deployment is failing repeatedly and getting the error saying it’s failed in tarball extraction phase. I have tried multiple times and every time I saw the issue in UI. 

I went through the /home/nutanix/data/logs/genesis.out logs to get more details on the issue. I found something interesting there. When we start the Prism central deployment, it first tried to download the prism central tarball and unzip it. One it’s unzipped then it’s start to convert the qcow2 file to image. when it start to convert the qcow2 → image , the command is configured with a timeout of 1800 sec. Please have a look into the below log line.

 

2024-07-01 08:55:17,702Z INFO 25030000 uvm.py:1606 Running cmd 6'/usr/bin/timeout', '1800', '/usr/local/nutanix/bin/qemu-img', 'convert', '-p', '-f', 'qcow2', '-O', 'raw', u'nfs://127.0.0.1/default-container-40804253832490/pc.2022.6.0.10-pc-boot.qcow2', u'nfs://127.0.0.1/default-container-40804253832490/pc.2022.6.0.10-pc-boot.img']

 

2024-07-01 08:55:17,791Z INFO 25030000 uvm.py:1606 Running cmd 0'/usr/bin/timeout', '1800', '/usr/local/nutanix/bin/qemu-img', 'convert', '-p', '-f', 'qcow2', '-O', 'raw', u'nfs://127.0.0.1/default-container-40804253832490/pc.2022.6.0.10-pc-home.qcow2', u'nfs://127.0.0.1/default-container-40804253832490/pc.2022.6.0.10-pc-home.img']

 

failure log lines

2024-07-01 09:25:06,157Z INFO 25030000 deployment.py:963 Busy waiting for /default-container-40804253832490/pc.2022.6.0.10-pc-home.qcow2->img     (63.26/100%)^M
2024-07-01 09:25:17,826Z INFO 25030000 deployment.py:963 Busy waiting for /default-container-40804253832490/pc.2022.6.0.10-pc-home.qcow2->img
2024-07-01 09:25:17,826Z INFO 25030000 deployment.py:965 Done Waiting for /default-container-40804253832490/pc.2022.6.0.10-pc-home.qcow2.qcow2 extract
2024-07-01 09:25:17,826Z INFO 25030000 deployment.py:989 Finished waiting for all procs
2024-07-01 09:25:17,827Z INFO 25030000 client.py:232 Creating stub for Ergon on 127.0.0.1: 2090
2024-07-01 09:25:18,071Z ERROR 25030000 deployment.py:1237 Unable to extract image
2024-07-01 09:25:18,071Z ERROR 25030000 deployment.py:1238 Error in deployment:Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/cluster/deployment/deployment.py", line 1108, in deploy_worke
Exception: Unable to extract image
 

 

If we compare the timestamp between start and when the error occurred, it’s exactly 30 mins and which is equivalent to 1800 sec. I am not sure why the timeout is configured by Nutanix but it’s putting our deployment to a failed state. 

Can you please let us know how to get rid of this timeout by configuring it to a higher interval or just remove the timeout check. All the required screenshots are attached.

Note:

Hypervisor Disk - 200 GB

CVM Disk - 700 GB

Data Disk - 400 GB

Container files to verify that the tar file download and extraction is successful.

 

I have the same issue...

I am also having this issue

One more seeing the same problem

 

+1 has anyone found a workaround?

+1 I notice the same issue and prism central is stuck on Tarball extraction process.

Hi here !

Same issue here 2 weeks ago. Reinstalling my CE cluster with differents disks works for me.

It seems to be a disks perf issue...

Hi here !

Same issue here 2 weeks ago. Reinstalling my CE cluster with differents disks works for me.

It seems to be a disks perf issue...

after installing phoenix.x86_64-fnd_5.6.1_patch-aos_6.8.1_ga - try to install prism and there are no compatible version of prism for deploy...

Not an issue, you can install it manually.

Here my how-to : https://juliendumur.fr/en/nutanix-ce-2-1-deploy-prism-central-pc-2024/

 

 

You can’t access downloads with your mynutanix account ?

unfortunately yes… 

edit

found on linkedin https://download.nutanix.com/ce/2020.09.16/ce-pc-deploy-2020.09.16.tar - will check it

@exe
do we need to reinstall the CE cluster again or any other work around is there? 
I tried with pc.2024.1.0.2.tar and stuck with tarbar extraction process. so i do have some warning about some WD disk for which nutanix throws an error or alert saying Unqualified disk. should i replace with SSD and check again ?

Thank you for you help. 

@MarcinK : this PC version isn’t 6.8 compatible.

@Nemani : havn’t try anything else than fresh reinstall; I would replace SSD yes.

@MarcinK :

Maybe you can try this one :

Prism Central : https://download.nutanix.com/downloads/pc/pc.2023.4.0.4/pc.2023.4.0.4.tar

Metadata : https://download.nutanix.com/pc/pc.2023.4.0.4/generated-pc.2023.4.0.4-metadata.json

@Exe 
I swapped the HDD with SSD in the third Node and re-installed the AHV and reformed the cluster post which still the prism central installation is stuck at “Tarball extration” process and it wont progress at all.

I used pc.2024.1.0.2.tar for prism central along with meta data on CE edition 6.8.1.

Any suggestions ?

@Nemani Can you provide some details about your disks configuration please ? (number of SSD/HDD and what did you install on them, AHV/CVMs)

@Exe 
I have couple of Dell R450 along with one old R210 Dell. 
R450’s have  7TB of HDD and 1 500 GB SSD
R210 have 1x 250 GB SSD and 2x 500GB SSD. 
I did installed the AHV community edition 6.8.1 formed the cluster without any issue.  Also FYI , I was able to form the cluster with previous CE edition and even installed the Prism central without any issue on the same Hardware. 

Shld i try any different verions of PC or even attempt to install PC in different way
https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v6_5:upg-vm-install-ahv-wc-t.html#ntask_wtr_xdz_ps

please let me know if any further information is needed. Thank you for the quick response.

@Exe 
I stopped the cluster on all of the nodes and when i navigated to my Prism element IP GUI which is open previously , it showed some 25 % completion of tarball extration process in 23 minutes. May be i shld have give some more time to it or stopping the cluster triggered the tarball extraction. 
Anyways i will reform the cluster again and attempt to install another version of PC and will wait for some 30 min and will update you. Stay tuned  thank you  Exe.

In my case, it took about 43min before failing.

Didi you select SDD for both Hypervisor and CVM during installation ? 

@Exe  
Yes. 

Reply


Terms & Conditions