Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Instance Provisioning - Failed to copy image down to cluster image datastore

Дата публикации: 23-09-2026 12:38:32

Hi,We configured a PoC environment consisting of three ProLiant DL380 Gen10 nodes and 3PAR storage for the datastores.VME Manager is in version 9.0.1 and the nodes are "HVM 1.3 Cluster on HVM/Ubuntu 24.04"On the nodes we configured 2 FC LUNs (lun001 of VMs and lun002 for images)lun001 (360002ac000000000000041f60001ce41) dm-1 3PARdata,VVsize=2.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw`-+- policy='service-time 0' prio=50 status=active|- 0:0:0:0 sdd 8:48 active ready running|- 0:0:1:0 sde 8:64 active ready running|- 0:0:2:0 sdf 8:80 active ready running`- 0:0:3:0 sdg 8:96 active ready runninglun002 (360002ac000000000000041f70001ce41) dm-2 3PARdata,VVsize=1.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw`-+- policy='service-time 0' prio=50 status=active|- 0:0:0:1 sdh 8:112 active ready running|- 0:0:1:1 sdi 8:128 active ready running|- 0:0:2:1 sdj 8:144 active ready running`- 0:0:3:1 sdk 8:160 active ready runningFrom the Manager interface we set up the two datastores, flagging the lun002 as Image Target.On the nodes we see the luns mounted as follow:/dev/mapper/lun001 2.0T 168G 1.9T 9% /mnt/d9c9f186-0a05-4fca-ae3d-cd9f8b91ed06/dev/mapper/lun002 1.0T 43G 982G 5% /mnt/8b5d7001-259e-4a41-af9c-36a66f4058adwe uploaded several ISOs on the manager (using the embedded location) without any problem.From those ISOs we managed to create several Windows and linux instances.We also managed to sysprep one of the Windows VM and upload a copy to the manager as a Golden Image using the 'Import as Image' option (qcow2 format, 26.7GB size). Now to the issue:If we try to provision a new instance using the golden image, the process fails during image upload after less than 2 minutes with the message "Failed to copy image down to cluster image datastore. Perhaps it is inaccessible? Check cluster configuration:".We are sure the image datastore is accessible and worked fine uploading the ISOs (althouth all the ISOs are smaller, less than 6GB).During our test we could see that a .tmp file is created on the datastore while the image is uploaded.What we noticed is that if we try to list the content of the datastore to check upload progression (using the file size) the ls command hangs at some point, until the image upload fails/timeout and the system cancel the .tmp fileWe noticed the same behaviour during instance provisioning using a bigger ISO, such as a SUSE o Red Hat ones. Any suggestion of what logs we can check to investigate this behaviour?best regards

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Failed to create synthetic full backup.015.1723-09-2026
2Backup problem - Failed to create synthetic full backup. See logs for details.013.123-09-2026
3hpe VME 9.0.2 Migration WIN VMware to HPVM06.4623-09-2026
4HVM Manager on VMware06.0323-09-2026
5No OpenSSH, no putty012.122-09-2026
6Host Shutdown Procedure for VME v908.8819-09-2026
7Infoblox installed on Morpheus KVM is not starting08.0222-09-2026
8Наполовину оффтоп, но позавчера (21 сентября 2026 года) редактор группы ...014.5623-09-2026
9Delays in starting jobs using the gen3 resource class012.8523-07-2026
10HPE Synergy update unmatched OS version with SSP08.1322-09-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 19.51. Источник: community.hpe.com.