Aria Suite Lifecycle fails deployment in in VMware Cloud Foundation mode with error, "Failed to expand vRSLCM disk size"
search cancel

Aria Suite Lifecycle fails deployment in in VMware Cloud Foundation mode with error, "Failed to expand vRSLCM disk size"

book

Article ID: 385978

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Environment

VCF 5.1

Cause

A reset is received by the SDDC Manager, from vCenter.

    2025-01-13T20:05:47.556+0000 INFO  [vcf_dm,bbbe0ad0d681e6c2,b5af] [c.v.e.s.c.v.vrslcm.VrslcmService,dm-exec-9]  Found request {"vmid":"7e9888d1-db11-4b41-aabf-a3b726b5c595","requestName":"lcmvadiskexpand","requestReason":"Expand VMware Aria Suite Lifecycle VA Data Disk","requestType":"lcmvadiskexpand","state":"FAILED","errorCause":"[{\"messageId\":\"LCMCOMMON80001\",\"message\":\"Generic system error\",\"eventId\":\"2110c081-bf4e-4cb2-bff4-2fb6edecfb22\",\"retry\":true,\"exceptionMessage\":\"javax.net.ssl.SSLException: SSL handshake from 0.0.0.0/0.0.0.0:44298 to vCenter.example.com/10.10.10.10:443 failed in 35 ms\",
    ...
    Caused by: javax.net.ssl.SSLException: SSL handshake from 0.0.0.0/0.0.0.0:44298 to vCenter.example.com/10.10.10.10:443 failed in 35 ms
    ...
    Caused by: java.net.SocketException: Connection reset

 

The disk operation fails on vCenter due to name resolution failure.

 

2025-01-13T19:07:25.078Z warning vpxd[20723] [Originator@6876 sub=VmProv opID=24ef-01-01] Unable to lookup ds for disk

2025-01-13T19:07:25.079Z info vpxd[20723] [Originator@6876 sub=pbm opID=24ef-01-01-01] No datastore for disk -101 in config, filePath ds:///vmfs/volumes/vsan:5219b39cb11aa6f6-d3a8201a1c52099d/2025-01-13T19:07:25.137Z info vpxd[20723] [Originator@6876 sub=VmCheck opID=24ef-01-01-01] CompatCheck results: (vim.vm.check.Result) [
-->    (vim.vm.check.Result) {
-->       host = 'vim.HostSystem:1aa1a640-48eb-489b-86d0-7fd20bfb1d7d:host-11',
-->    }
--> ]
2025-01-13T19:07:25.396Z info vpxd[20723] [Originator@6876 sub=VmProv opID=24ef-01-01-01] Creating VM with spec (vim.vm.ConfigSpec) {
-->    name = "vrLCM_VM",
-->    version = "vmx-13",
-->    createDate = "2025-01-13T19:07:25.079118Z",
-->    uuid = "421b2917-85bf-79d8-5b51-b42d65403805",
-->    instanceUuid = "501b809d-f0fe-8d66-1df2-c1ac0c045f4b",
-->    guestId = "vmwarePhoton64Guest",
-->    files = (vim.vm.FileInfo) {
-->       vmPathName = "ds:///vmfs/volumes/vsan:5219b39cb11aa6f6-d3a8201a1c52099d/6d648567-b046-56b9-487f-e4434bf1ffc0/vrLCM_VM.vmx",
-->    },

2025-01-13T19:07:26.059Z warning vpxd[37568] [Originator@6876 sub=vmomi.soapStub[42] opID=TaskLoop-host-11] SOAP request returned HTTP failure; <<io_obj p:0x00007f0f581a2d78, h:104, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-11/vpxa>, method: waitForUpdates; code: 500(Internal Server Error)

2025-01-13T19:07:26.126Z warning vpxd[20723] [Originator@6876 sub=vpxUtil opID=24ef-01] getaddrinfo failed; host: ESXi.example.com, e: N7Vmacore15SystemExceptionE(Name or service not known)

Resolution

Check that valid forward and reverse DNS entries exist for VCF components, and specifically, the ESXi system named in the error message, "ESXi.example.com."

Check that vCenter is configured with the correct DNS servers for the environment.

Check that a firewall or other network security system is not blocking DNS traffic.