Hi,
Need assistance with PoC Environment, HPE VME + Veeam.
HPE VME v. 8.0.11, 3 host Cluster (Cisco UCSC-C220-M6S) Agent Version: 3.1.0. Veeam VSA Build 13.0.1.180 with veeam-platform-service-hpemorpheusvme-13.1.0.206-0.el9.x86_64.BETA.bndl. Cluster storage NFS, iSCSI (GFS2). Network configured with 3 vlan. HPE Morpheus Essentials added to Managed Servers. HPE Morpheus VM Essentials worker deployment failed with Error:
"Failed to find uploaded worker VM images: Error occured while deserializing the response",
"Worker veeamworker test failed: Error occured while deserializing the response".
-VeeamBackupLogs\veeamsa\VeeamBackup\Plugins log:
2025-12-08 09:13:06.0780 00061 [277246] INFO | [Worker][2c36e03e-0252-4330-9dad-fc187151eaab][veeamworker]: Save worker 2c36e03e-0252-4330-9dad-fc187151eaab data to DB
2025-12-08 09:13:06.1323 00061 [277246] ERROR | [Worker][2c36e03e-0252-4330-9dad-fc187151eaab][veeamworker]: Worker veeamworker test failed: Error occured while deserializing the response
Thanks,
-
momcilodosenovic
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 08, 2025 10:35 am
- Full Name: Momcilo Dosenovic
- Contact:
-
EvgenyBaev
- Veeam Software
- Posts: 23
- Liked: 2 times
- Joined: Apr 11, 2019 11:06 am
- Full Name: Evgeny Baev
- Contact:
Re: HPE-VME-Failed deploy worker
Hello, momcilodosenovic
Could you please provide the whole error stack from plugin logs? Or provide the whole Veeam.HPEMORPHEUSVME.PlatformSvc.log if possible.
Could you please provide the whole error stack from plugin logs? Or provide the whole Veeam.HPEMORPHEUSVME.PlatformSvc.log if possible.
-
momcilodosenovic
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 08, 2025 10:35 am
- Full Name: Momcilo Dosenovic
- Contact:
-
EvgenyBaev
- Veeam Software
- Posts: 23
- Liked: 2 times
- Joined: Apr 11, 2019 11:06 am
- Full Name: Evgeny Baev
- Contact:
Re: [BETA] [HPE] HPE-VME-Failed deploy worker
Hello, momcilodosenovic
Thank you for providing the log bundle — it was indeed very helpful.
We have identified that the issue occurs right at the start of the worker deployment process, specifically when we attempt to check for already uploaded worker images (to avoid re-uploading them).
Here’s a summary of our findings:
1) We issue a GET /api/virtual-images request.
2) The deserialization of the response fails because, for one of your virtual images, we receive "isCloudInit": null.
For example:
2025-12-05 13:32:00.8951 00028 [277246] ERROR | [Worker][dd94db6d-9022-4517-b757-df67eaf74748][VeeamWorker]: Failed to find uploaded worker VM images: Error occurred while deserializing the response: Veeam.NutanixBackup.RestSharp.InternalResponseDeserializationException: Error occurred while deserializing the response
2025-12-05 13:32:00.8951 00028 [277246] ERROR | [Worker][dd94db6d-9022-4517-b757-df67eaf74748][VeeamWorker]: ---> Newtonsoft.Json.JsonSerializationException: Error converting value {null} to type 'System.Boolean'. Path 'virtualImages[0].isCloudInit', line 1, position 251.
3) According to the HPE REST API specification, this field should not be nullable - only true or false values are expected.
4) When reviewing all virtual image types on version 8.0.11, I noticed that the "Is Cloud Init Enabled?" checkbox is present in the UI for all images except for those of type "PXE boot".
Could you please review your virtual images and confirm whether the "Is Cloud Init Enabled?" checkbox is shown for all of them (if the number of images is not too large)?
If you do not have any "PXE boot" images, could it be that some images were uploaded using an older version of HPE software?
We can implement a workaround on our side for this scenario. However, ideally the HPE team should update their API specification or implementation, since it appears "isCloudInit": null can occur in practice.
As a potential workaround, you may try the following:
1) Go through the "Edit virtual image" wizard for the affected image(s) - this might resolve the issue if "Is Cloud Init Enabled?" checkbox is present now.
2) If that does not help, try deleting the virtual image(s) missing the "Is Cloud Init Enabled?" checkbox and attempt the operation again.
3) If deleting virtual images is not an option, please let us know, and we can provide a fix on our side.
Please let us know if you need any further assistance, or if you are able to identify which images are affected.
Thank you again for your collaboration!
Thank you for providing the log bundle — it was indeed very helpful.
We have identified that the issue occurs right at the start of the worker deployment process, specifically when we attempt to check for already uploaded worker images (to avoid re-uploading them).
Here’s a summary of our findings:
1) We issue a GET /api/virtual-images request.
2) The deserialization of the response fails because, for one of your virtual images, we receive "isCloudInit": null.
For example:
2025-12-05 13:32:00.8951 00028 [277246] ERROR | [Worker][dd94db6d-9022-4517-b757-df67eaf74748][VeeamWorker]: Failed to find uploaded worker VM images: Error occurred while deserializing the response: Veeam.NutanixBackup.RestSharp.InternalResponseDeserializationException: Error occurred while deserializing the response
2025-12-05 13:32:00.8951 00028 [277246] ERROR | [Worker][dd94db6d-9022-4517-b757-df67eaf74748][VeeamWorker]: ---> Newtonsoft.Json.JsonSerializationException: Error converting value {null} to type 'System.Boolean'. Path 'virtualImages[0].isCloudInit', line 1, position 251.
3) According to the HPE REST API specification, this field should not be nullable - only true or false values are expected.
4) When reviewing all virtual image types on version 8.0.11, I noticed that the "Is Cloud Init Enabled?" checkbox is present in the UI for all images except for those of type "PXE boot".
Could you please review your virtual images and confirm whether the "Is Cloud Init Enabled?" checkbox is shown for all of them (if the number of images is not too large)?
If you do not have any "PXE boot" images, could it be that some images were uploaded using an older version of HPE software?
We can implement a workaround on our side for this scenario. However, ideally the HPE team should update their API specification or implementation, since it appears "isCloudInit": null can occur in practice.
As a potential workaround, you may try the following:
1) Go through the "Edit virtual image" wizard for the affected image(s) - this might resolve the issue if "Is Cloud Init Enabled?" checkbox is present now.
2) If that does not help, try deleting the virtual image(s) missing the "Is Cloud Init Enabled?" checkbox and attempt the operation again.
3) If deleting virtual images is not an option, please let us know, and we can provide a fix on our side.
Please let us know if you need any further assistance, or if you are able to identify which images are affected.
Thank you again for your collaboration!
Who is online
Users browsing this forum: No registered users and 2 guests