VMware vRealize CloudClient 4.7 Release Notes

 

vRealize CloudClient 4.7 | 11 APR 2019 | Build 13182508

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

The vRealize CloudClient 4.7 release includes resolved issues and support for Site Recovery Manager 8.1.2.

Resolved Issues

  • Delay when using Cloud Client 4.6 to change machine reservation

    Using Cloud Client 4.6 to migrate the vRealize Automation managed machines to a new reservation and storage results in a significant delay before completion. The delay occurs while Cloud Client iterates all VM's to find the one that matches the user input.

    This issue has been resolved in this release.

  • Unable to find storagePath error after migrating vRealize Automation machines

    After migrating vRealize Automation managed machines from one cluster to another within the same vCenter, using the command vra machines change reservation to correct the reservation and storagePath for the machines returns the following error:

    "Error: Unable to find a StorageInputModel by the name or id..."

    This issue has been resolved in this release.

  • Unable to reconfigure the memory of a machine. Same feature works in the UI.

    While processing the reconfiguration request, the serialization of storage and network object changes the initial character in the field names to lowercase. The initial character should be uppercase.

    This issue has been resolved in this release.

Known Issues

  • Deployment actions for Scale In and Scale Out do not support template generation

    The vra deployment action execute command for Scale In and Scale Out requires the user to specify the component names and desired number of instances as a request parameter but does not provide a template with the component names populated.

    Workaround: Use the vra blueprint detail command to retrieve the component names

  • Deployment action for Change Security is not supported

    When you attempt to use deployment action for Change Security, the operation fails with an error message.

    Workaround: None