Known Issues & Limitations
This page lists existing known issues of the Enterprise Service Cloud and suggests workarounds, if applicable.
List of issues:
[Swisscom RHEL 9] recovery of files and folders is not possible
The recovery of single files and folders is not possible on VMs running with the Swisscom RHEL 9 blueprint. This is due to a technical limitation on the backup infrastructure. This limitation does not affect the recovery of a complete VM.
Swisscom is working with the vendor on a permanent solution.
Custom Properties on Swisscom Blueprints (RHEL and Windows)
On the "Swisscom Blueprints" (Swisscom RHEL 8|9, Swisscom Windows 2019|2022) the customer specific Custom Properties (link) are shown as duplicates. This behaviour is expected and can't be changed. The properties are duplicated automatically by vRealize Automation, once for the Deployment and once for the Machine.
If the Custom Properties are created as mandatory, both properties will be mandatory in the blueprint as well.
Example Swisscom RHEL 9 blueprint with 2 Custom Properties (MyProperty1 -> string, MyProperty2 -> boolean). 
After provisioning, the first set of properties will be assigned to the deployment. 
The second set of properties will be assigned to the virtual machine. 
AltGr key not working on Linux VMs with the VMRC console
When using in vRA the VMRC console to access a Linux VM, the "AltGr" key is not working with the Swiss keyboard layout. All "AltGr" special characters like @, #, |,[ etc. won't work.
Workaround:
Use in vRA the remote console (Web client) to access your Linux VM.
Portal sessions not closed on logout
After logging out of the Swisscom Portal, one session from the backend gets not closed properly, therefore you can't login with a different user afterwards.
Workaround:
Reopen your browser or logout in vRA & Swisscom Cloud Portal separately.
Change the network on a vNic is not possible
If one changes the network on any vNIC that is linked to an external IPAM, the vNIC will not actually be placed on that network.
Workaround:
Remove the vNic in a first step and add a vNic (attached to the new network) in a second step.
Adding and removing vNics at the same time is not possible
If one is adding and removing one (or multiple) vNics in the same reconfigure action, the machine gets an IP outside of the network range.
Workaround:
Perform two reconfigure actions where in one the vNic(s) are removed and in the other the vNic(s) are added
Adding vNic on reconfigure does not customize the guest OS
When adding an additional network interface after provisioning (using the day-2 operation "Reconfigure"), the guest operating system does not get customized and therefore the IP will not be properly configured on the guest.
Workaround:
Login to the guest system and configure the additional network interface manually. All necessary information (such as IP address, gateway, broadcast ... ) can be retrieved from the vRA GUI (Virtual Machine detail view -> Network Tab)
Requests fail with the Error Message "I/O Error on POST Request"
Occasionally, a deployment fails with the following error message:
Request initialization failed: I/O Error on POST request for "https://cmp.entcloud.swisscom.com/composition-service/api/requests/request_initializer": Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out
In rare cases, this error message may occur due to a high number of tasks being processed at the same time, during heavy load on our vSphere backend systems.
Workaround:
Re-trigger your deployment request some minutes later. The deployment should run successfully.
History of deleted child elements is not visible
The history of deleted child deployments (e.g. a deleted NFS Container as child of a File Service Premium deployment) is not visible after the element has been deleted.
This is a known issue in v7.5 of vRealize Automation. The history is saved on the child deployment itself, and when the object is deleted the history is also removed from the parent deployment.
This issue is aimed to be fixed with the next version of vRA.
Machine reconfiguration fails with error message "Could not allocate the required storage or memory resources"
During ongoing backup jobs, a reconfigure action can fail with following exception.
Machine reconfigure request failed - Could not allocate the required storage or memory resources. Relocation of existing disks is not supported
Workaround:
Retry after several hours (depending on VM size) when the backup job completed.