CloudForms not appending number to VM name after 5.3.4 update

Issue

• With latest CF 3.1 when deploying a service, the VM name does not get a number appended to it to ensure it is unique as it did before. E.g. If a request to create a VM named TestVM is loaded, and a VM named TestVM already exists on the provider the VM TestVM_0001 should be created but instead the request fails with an error stating that a VM with the name TestVM already exists. The error is also only visible in the automation log and no useful information is displayed in the CFME requests list in the web frontend.