Using "." in VM Custom Name in blueprint causes additional Cloud.vSphere.Disk disks to be created into a different VM folder on Datastore.

Products

• VMware vRealize Automation 8.x

Issue/Introduction

When adding additional Cloud.vSphere.Disk disks to some cloud templates, those additional disk vmdk files are not being added into the standard VM folder in /vmfs/volumes, instead they are being added to a folder on their own which is given the VM name.

For example we see the additional1.vmdk added to a new folder rather than the existing VM folder

[root@ESXI-1:/vmfs/volumes/vsan:52311403c038a0cf-f004f83508fe2679/f5614f66-c8f3-c0d6-fd2d-f4c7aa21c9c6] ls -lrt
total 0
-rw-------    1 root     root           588 Jun  3 23:04 additionaldisk1.vmdk

Here we see the VM folder that is created on deployment:

[root@ESXi-1:/vmfs/volumes/vsan:52311403c038a0cf-f004f83508fe2679/ec614f66-8e1d-8bb8-8382-f4c7aa21c9c6] ls -lrt
total 84224
-rw-r--r--    1 root     root             0 May 23 15:34 VM-Name-example.domain.com.vmsd
-rw-r--r--    1 root     root           576 May 23 15:34 VM-Name-example.domain.com-352d374d.hlog
-rw-------    1 root     root      83886080 May 23 15:34 vmx-VM-Name-example.is.e-d4a6a72c992957aece8d9f8e8012ca475bf3d11b847828de877c6b7dfc2313f8-1.vswp
-rw-------    1 root     root             0 May 23 15:34 VM-Name-example.domain.com.vmx.lck
-rw-------    1 root     root             0 May 23 15:34 VM-Name-example.domain.com-587b8a6f.vswp.lck
-rw-------    1 root     root           308 May 23 15:34 VM-Name-example.domain.com-587b8a6f.vswp
-rw-------    1 root     root         53248 May 23 15:34 _ovfenv-VM-Name-example.domain.com.iso
-rw-------    1 root     root        270840 May 23 15:34 VM-Name-example.domain.com.nvram
-rw-------    1 root     root           611 Jun  3 23:04 VM-Name-example.domain.com.vmdk
-rwxr-xr-x    1 root     root          3631 Jun  3 23:04 VM-Name-example.domain.com.vmx~
-rwxr-xr-x    1 root     root          3634 Jun  3 23:04 VM-Name-example.domain.com.vmx
-rw-r--r--    1 root     root        238987 Jun  4 09:39 vmware.log
-rw-r--r--    1 root     root          8192 Jun  4 09:59 vra-rocky-8-64bit.domain.com.scoreboard
[root@ESXI-1:/vmfs/volumes/vsan:52311403c038a0cf-f004f83508fe2679/ec614f66-8e1d-8bb8-8382-f4c7aa21c9c6]

Environment

Custom input for a blueprint like the example below providing the input VM name full FQDN

Cause

When the input for the FQDN uses the full name and includes a "." then it causes the additional disks to be created into a different VM folder on the Datastore. Issue does not occur if we use the short name

Resolution

Engineering have identified the issue and will this will be fixed in the 8.18.1 release.