058065

vRealize Automation 7.0.1 Release Notes

Updated on: 17 MAY 2016

vRealize Automation | 15 MAR 2016 | Build 3622989

Check regularly for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vRealize Automation 7.0.1 is a patch release that includes a number resolved issues and an important security update.

System Requirements

For information about supported host operating systems, databases, and Web servers, see the vRealize Automation Support Matrix.

Installation

For prerequisites and installation instructions, see Installing vRealize Automation.

Before You Upgrade

New vRealize Automation features and innovations required several platform-level enhancements. As a result, certain upgrade scenarios require additional assistance. To ensure the best possible upgrade experience, go to the vRealize Automation Upgrade Assistance webpage before you begin the upgrade process.

Resolved Issues

The resolved issues are grouped as follows:

Security Issue

  • CVE-2015-7547 glibc getaddrinfo() stack-based buffer overflow
    The issue is resolved.

Installation Issues

  • CVE-2015-7547 glibc getaddrinfo() stack-based buffer overflow
    The issue is resolved.

  • On Windows Server 2012 R2, the Prerequisite Checker incorrectly shows Microsoft Distributed Transaction Coordinator Service as fixed
    A warning appears in the Prerequisite Checker for Microsoft Distributed Transaction Coordinator Service. After you click Fix, it appears as fixed. Rerunning the Prerequisite Checker causes the warning to reappear.
    This issue is resolved.

  • IaaS installation logs are not collected if an IaaS component is not installed in the default installation location
    The IaaS installation logs are created in the default installation folder, %PROGRAMFILES(x86)%\VMware\vCAC\. If all IaaS components are installed in a nondefault location, the log bundle collected from the vRealize Automation appliance does not include the IaaS installation log files.
    This issue is resolved.

  • During installation or upgrade, a validation error message appears and the installation fails
    The following error message appears before the installation fails: The Windows log on identity [DOMAIN\USER] could not be verified as having the “Log on as a service” right (Windows Local Policy).
    This issue is resolved.
  • During the installation or upgrade of vRealize Automation 7.0, RegistryKeyPermissionCheck warning appears even though the user has rights
    This issue is resolved.

  • During installation or upgrade, a wrong certificate error message appears and the installation fails.
    When you use the Installation Wizard to install vRealize Automation, the case of the name you enter for the first vRealize Automation appliance must match the case of the name you enter when you add additional appliances. If the cases of the two names are different, for example, vRAapp and vraapp, an error message about wrong credentials appears after you join an additional appliance to the cluster and the installation fails.
    This issue is resolved.

Upgrade Issues

  • Java exception error occurs when you use the Identity Stores Migration Tool to reassign a tenant administrator
    This issue occurs because a synchronized user administrator in the setup directory causes the reassignment to fail.
    This issue is resolved.

  • The vRealize Orchestrator service is unavailable after you upgrade to vRealize Automation 7.0
    The upgrade breaks the connection between the vRealize Orchestrator and the configured Administrator group.
    Information to resolve this problem is available in the vRealize Automation 6.2.x to 7.0.1 and 7.0 to 7.0.1 Upgrade Guides.

  • After you upgrade to vRealize Automation 7.0, duplicate catalog items for the same business group appear in the catalog
    This issue is resolved.

  • Error appears when you run the Identity Stores Migration Tool
    When you run the Identity Stores Migration Tool, the following error might appear:
    ERROR: MigrateIdentityStores: Tenant 'vsphere.local': Can not create directory '': Could not join domain Error occurred while joining domain. Verify Domain Admin user name and password is correct, and the user name is the sAMAccountName.
    This issue is resolved.

  • When you upgrade the Manager Service and DEM Orchestrator system, an error message appears and the Model Manager Web host cannot be validated
    The following error appears if you change the name of the load balancer in the ManagerService.exe.config file:
    Distributed Execution Manager "NAME" Cannot be upgraded because it points to Management model web host "xxxx.xxxx.xxxx.net:443", which cannot be validated. You must resolve this error before running the upgrade again: Cannot validate Model Manager Web host. The remote certificate is invalid according to the validation procedure.
    This issue is resolved.

  • If you add the embedded vRealize Orchestrator as an endpoint in vRealize Automation 6.x, the endpoint stops working after you upgrade to vRealize Automation 7.0
    In vRealize Automation 6.x, the embedded vRealize Orchestrator is available at https://hostname:8281/vco. The upgrade changes the embedded vRealize Orchestrator URL from https://hostname:8281/vco to https://hostname/vco. After the upgrade, the connection to the embedded vRealize Orchestrator that is added as an endpoint in vRealize Automation 6.x is broken because the URL is changed.
    The vRealize Automation Upgrade document is updated to include the correct URL.

  • If you upgrade a deployment that contains blueprints that specify a private network, with a private deployment present, this situation causes issues during and after upgrade
    Private networks and private network profiles are not supported in vRealize Automation 7.0.
    If you have private networks specified in 6.2.x blueprints, you can remove the private network specifications from the blueprints before the upgrade, and remove all dependent deployments. If you do not remove the private network specifications from the blueprints, the upgrade tool removes them and leaves the impacted blueprints in a draft state. You must then correct and republish those blueprints after upgrade.
    This issue is resolved.

Configuring and Provisioning Issues

  • When you use Bulk Import to import a unmanaged virtual machines into vRealize Automation, a failure during the import process can delete the machines from vCenter Server
    This issue is resolved.

  • Subscriptions for the EventLog Default Event topic do not receive any events and do not trigger a vRealize Orchestrator workflow
    This issue is resolved.

  • Some machine provisioning workflows generate errors related to workflow subscriptions and the event broker service
    This issue is resolved.

  • When you run the workflow subscriptions wizard, an internal error appears when you select Run based on conditions
    When you run the workflow subscriptions wizard and select Run based on conditions for a new or edited workflow subscription, and select either All of the following or Any of the following, but add only one condition, no validation error appears and you are able to continue. When you click Finish, an internal error appears, and the subscription is not saved.
    This issue is resolved.

  • When you change the name of the nested blueprint, you break the NIC associations to the blueprint and this causes provisioning to fail
    When when you edit a blueprint that contains a nested blueprint and where a network profile and specified NIC are associated to a vSphere machine component, and change the name of the nested blueprint, the name change breaks the NIC associations to the blueprint, As a result, the provisioning operation fails.
    This issue is resolved.

  • When you submit a request for a catalog item, the request fails and the submit button disappears
    This issue is resolved.

  • The status of a machine on the Managed Machines page might erroneously appear as Missing for some time after provisioning
    After the system performs a subsequent data collection on the compute resource that hosts the missing machine, the correct machine status appears.
    This issue is resolved.

  • You cannot add or delete property groups after a blueprint component is added
    After you add a blueprint component that you create or edit in the design canvas, and click Finish, you can no longer save any modification to the property groups of the outer blueprint.
    This issue is resolved.

  • When you change a quota setting in a blueprint, the setting change is removed when you publish the blueprint
    When you open and save a blueprint to which a quota setting is already assigned, the quota is reset to unlimited.
    This issue is resolved.

  • Network component names do not appear properly in the Catalog Items page
    Software code appears in place of the name of the network type on the Catalog Items page in a localized UI.
    This issue is resolved.

  • When you create a blueprint with a cloned machine by using the REST API, the Clone from snapshot menu is unavailable
    On the Build Information tab, the Clone from snapshot menu is unavailable, and you cannot make a selection from the drop-down menu.
    This issue is resolved.

  • When you deploy a linked clone VM after changing the snapshot target, error message about the snapshot appears
    For example, if you add a linked clone from a snapshot of VM1 to a blueprint and save it, and then change the snapshot to VM2, the change from VM1 to VM2 does not take effect and the following error message appears: CloneVM : Specified snapshot does not exist. Clone operation cancelled.
    This issue is resolved.

  • When you update a blueprint the load balancer settings revert to default values
    When you change a load balancer value in a blueprint and navigate away from the page, the changed values revert to the default values.
    This issue is resolved.

  • When you request a catalog item that contains an on-demand 1-to-1 NAT network and and add default VM instances, the NAT rules are not created for the added VMs
    If a blueprint contains VM instances and an NSX on-demand NAT 1-to-1 network component, A problem happens when a user requests that catalog item and adds more VM instances to the VMs specified in the blueprint. When this happens, the 1-to-1 NAT rules are not created for the additional VMs. If the user does not change the number of VM instances, the deployment with 1-to-1 NAT configuration is correct for all VMs.
    This issue is resolved.

  • Unable to provision a vSphere machine by using NAT 1-to-1 when the number of machine instances specified in the nested blueprint is not overridden in the outer blueprint
    If you add a nested blueprint that contains a vSphere machine component with minimum instance set to 2 or higher and the maximum instance blank, add a NAT 1-1 network component, and add a NIC on the vSphere machine component in the nested blueprint using the NAT 1-1 settings, provisioning from the published outer blueprint fails with the following error:
    Request [9d7b7c07-3e04-4d5b-8ae6-be4eef4d2eca]: Index: 1, Size: 1 (stacktrace attached)
    This issue is resolved.

  • Incorrect currency symbol might appear when vRealize Business Standard Edition is integrated with vRealize Automation
    If the vRealize Business Standard appliance is configured to use currencies that are different from those configured in the Windows Regional Settings of the operating system where the IaaS server is installed, the incorrect currency symbol appears in the reclamation request and in the body of the email.
    This issue is resolved.

  • When using bulk import, "" error appears
    When you import a machine, the following error message appears: Unable to load provisioning workflow. This occurs when the final catalog registration step fails. Upon failure, IaaS attempts to destroy the machine when the registration retry limit is reached.
    This issue is resolved.

  • When you request blueprints on a server that is processing many concurrent requests, the request might sometimes fail with PROVIDER_FAILED status
    During times of heavy provisioning, some requests remain in the Machine Activated state and eventually the PROVIDER_FAILED message appears. This issue occurs because of SocketTimeoutExceptions when the connections between the Java services and Windows services are deadlocked.
    This issue is resolved.

  • When you request blueprints that contain NSX security components on a heavily loaded server, the request might sometimes fail with PROVIDER_FAILED status
    During times of heavy provisioning, some requests fail to provision VM components. The following message appears in request details: Failed to configure one or more network and security settings. Error: One or more errors occurred.
    This issue is resolved.

  • Virtual machine is deleted during reprovisioning when a datastore is moved from one SDRS cluster to another
    When a datastore is moved from one SDRS cluster to another, inventory data collection updates the storage paths of the disks. However, the VirtualMachine.Storage.Cluster.Name custom property of the virtual machine that is being reprovisioned is not updated with the new storage paths of the disks, and the machine is deleted when it is reprovisioned.
    This issue is resolved.

  • Software provisioning in Windows 8, Windows 2000 R2, and Windows 10 requires that .NET 3.5 be installed on the template machine prior to installing the software bootstrap agent
    .NET 3.5 is required only when users are preparing the templates for software provisioning. The .NET 3.5 requirement does not apply to machine-only provisioning.
    This issue is resolved.

  • The change certificates command does not deploy the new certificate on a standalone agent server
    A new certificate is not deployed when the change IaaS Web Server or Manager Service certificate command is run in an environment where there is at least one IaaS Server that has only agents installed. When the certificate is self-signed or not trusted by default on the IaaS Web Servers, the trust needs to be established manually.
    This issue is resolved.

  • After you change the SSO administrator password, the vco-server service does not start
    When the SSO administrator password is changed, all services are restarted, but vRealize Orchestrator cannot get a license because the request is made before the license service starts. Exception messages from the vco-server service appear, and vRealize Orchestrator does not start.
    This issue is resolved.

  • Internal error appears when you create a new XaaS blueprint and add a Required, Read only, or Visible constraint
    When you specify a constant value for one of the boolean constraints of Required, Read only, or Visible, and click Apply, an Internal Error message appears. This issue applies to the XaaS components that support multiple values such as Checkbox list, Dual list, and Search.
    This issue is resolved.

  • Internal Server Error appears while configuring Directories Management
    When you select individual groups or Active Directory containers, such as domain or organizational unit, that contain groups on the Select the groups (users) you want to sync page, an the error message Internal Server Error appears if the same group is resolved by more than one group DNs entry on that page.
    This issue is resolved.

  • Proxy settings do not work correctly for vCloud Director or vCloud Air endpoints
    When you connect to the endpoint during data collection, the system ignores proxy settings used when creating vCloud Director or vCloud Air endpoints. This might cause data collection failures, if the proxy is required to connect to the endpoint address.
    This issue is resolved.

Known Issues

The known issues are grouped as follows:

Known issues not previously documented are marked with the * symbol.

Installation Issues

  • New Cannot install Common Components Catalog
    Installation of the Common Components Catalog might fail on vRealize Automation IaaS Manager Service machines.

    Workaround: Add the IIS Management Console role service to the Manager Service machine. To add the role service, navigate to the Control Panel option to turn Windows features on or off. Under Internet Information Services (IIS), expand Management Tools, and select IIS Management Console.

  • New Double quote marks not allowed in the administrator password
    In addition to the special characters listed in the installation documentation, do not include double quote marks (") in vRealize Automation administrator passwords.

    Workaround: None. Do not include double quote marks in the administrator password.

  • New Distributed Transaction Coordinator requirement
    Provisioning a machine in vRealize Automation might fail with the following error:
       Error executing query usp_SelectHostReservation
    The error occurs when a Distributed Transaction Coordinator (DTC) requirement has not been enabled on the vRealize Automation SQL Server and the Model Manager portal machines.

    Workaround: Enable DTC on vRealize Automation SQL Server and Model Manager machines by following the guidelines in Knowledge Base article 2038943.

  • The vRealize Automation appliance page does not load correctly
    When using Internet Explorer 11 in Windows 2012 R2, the Web interface page for the vRealize Automation appliance does not load correctly.

  • The Prerequisite Checker's validations for IIS Server Windows Authentication work only for the Default Web Site where the Windows Authentication settings are not modified after the installation of IIS components
    If the Default Web Site's Windows Authentication settings are modified after installing IIS components, the vRealize Automation 7.0 installation fails because the prerequisite checker does not detect the change.Before you install vRealize Automation 7.0, verify in the IIS Manager that you have administrative privileges to change IIS settings in the Internet Information Services (IIS) Manager or the Server Manager.

    Workaround: For information about how to resolve this issue, see Knowledge Base 2138781.

Upgrade Known Issues

  • When you upgrade a replica server from vRealize Automation 7.0 to 7.0.1, the replica server must be in sync with the master server. If the replica server is not in sync, the PostgreSQL service on the replica cannot start, and the upgrade fails.

    Workaround: After you upgrade the master node, run the following commands on each replica node before you upgrade a replica instance:

    1. rm -rf /storage/db/pgdata_backup
    2. vcac-vami psql-set-replica

  • Certain blueprints cannot be fully upgraded due to failures in updating catalog resources*
    Upgraded multi-machine blueprints that contain on-demand networks or load balancer settings might not be fully functional after you upgrade to vRealize Automation 7.x.

    Workaround: After you upgrade, delete and re-create the deployments associated with multi-machine blueprints. All associated NSX Edge cleanup work must be done in NSX.

  • When you upgrade from vRealize Automation 6.2.0 to 7.0, vPostgres upgrade fails, and an error message appears
    If the system has a corrupt RPM database, this error message appears during the upgrade process: Failed to install updates(Error while running pre-install scripts).

    Workaround: For information about how to recover from an RPM database corruption, see the article "RPM Database Recovery" at the RPM Web site RPM. After you fix the problem, run the upgrade again.

  • When you run the Prerequisite Checker, the checker fails with a warning about RegistryKeyPermissionCheck, but the instructions to correct the error do not work during installation
    The Prerequisite Checker fails because it is case-sensitive for the user name.

    Workaround: Temporarily change the user you specified to run the Management Agent Service on the Windoows machine to another user, and then change back to the original user by using the correct case for the user name.

  • When you change the host name to a different name after the Active Directory connection is initialized, the Active Directory connector is unusuable and Active Directory fails
    You should not change the virtual appliance host name after the Active Directory connection is initialized. You can change the load balancer name in the vRealize Automation appliance management console by selecting vRA Settings > Host Settings.

  • When you upgrade the Manager Service and DEM Orchestrator system, a name validation error message appears and the Model Manager Web host cannot be validated
    The following error appears if the name of the load balancer changes in the ManagerService.exe.config file:
    Distributed Execution Manager "NAME" Cannot be upgraded because it points to Management model web host "xxxx.xxxx.xxxx.net:443", which cannot be validated. You must resolve this error before running the upgrade again: Cannot validate Model Manager Web host. The remote certificate is invalid according to the validation procedure.

    Workaround: Make the following changes to the ManagerService.exe.config configuration file. The default location is at C:\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config.
    Change the registry values for all DEM instances. For example, the DEM instances in the following registry entries should both be updated.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware vCloud Automation Center DEM\DemInstanceId02]
    "Name"="DEM"
    "Role"="Worker"
    "RepositoryAddress"="https://host_name:443/repository/"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware vCloud Automation Center DEM\DemInstanceId03]
    "Name"="DEO"
    "Role"="Orchestrator"
    "RepositoryAddress"="https://host_name:443/repository/"

Configuring and Provisioning Issues

  • In a high availability environment, Horizon fails to perform authentication after failover*

    Workaround: After failover, restart the vRealize Automation appliance to restore authentication.

  • When you save host name and certificate settings in the vRealize Automation appliance management interface, an error message appears*
    This message appears when you close the installation wizard and configure vRealize Automation manually using the vRealize Automation appliance management interface. When you click Save Settings after you specify the host name and certificate, the following message appears: Error calling external command.

    Workaround: Click the Refresh button.

  • Unable to change disk size while requesting a machine from the catalog*
    When you attempt to change the disk size of a machine during the request process, the Capacity text box becomes unavailable. This happens because you cannot change the disk size specified on the blueprint for the machine.

    Workaround: If you want to add storage capacity to a machine, you can add additional disks at request time.

  • Required but empty software component property*
    It is possible to create a blueprint that contains a software component with a required property but no means for a requester to provide a value for the property. For example, a software author creates a required software component type property with no default value. Then a blueprint author creates a blueprint that contains the required property but specifies the property to either not be shown in the request form, or not to be overridden. This creates a request form with an empty but required property but with no means for a requester to provide a value. When requesters using this request form click Submit, they might see a Correct the highlighted errors message, but there are no highlighted properties on the page to correct. If the requester clicks Submit again, the error message disappears and the system submits the request without any value for the required property.

    Workaround: To prevent this situation, a blueprint author can select both the Overrideable and the Show in request check boxes on the software component configuration.

  • Adding Active Directory Groups in VMware vRealize Automation 7.x containing the pound (#) symbol fails*

    Workaround: See Knowledge Base 2142946

  • IP address for an Amazon Web Services virtual machine is unavailable in the catalog API after you provision a machine*
    After you use the vRealize Automation catalog API to provision an Amazon Web Services virtual machine, you cannot get the IP address for the machine using the catalog API.

  • When you delete a tenant that has a large number of groups, the process might time out*
    When the system fails to delete a tenant completely because the process times out, do not run the delete process again. After the process times out, the remaining tenant data eventually triggers a delete routine that completes the process automatically.

  • Some components might not function as expected after you drag an existing inner blueprint into a current outer blueprint*
    Component settings can change depending on which blueprint the component is on. For example, if you include security groups, security tags, or on-demand networks at both the inner and outer blueprint levels, the settings in the outer blueprint override those in the inner blueprint. Network and security components are supported only at the outer blueprint level except for existing networks that work at the inner blueprint level.

    Workaround: Add all your security groups, security tags, and on-demand networks only to the outer blueprint.

  • If you enter a comma (,), a backslash (\), or a space between two valid characters in the root password while deploying the vRealize Automation appliance for the first time, the setup process fails when you use the wizard to set up a High Availability environment.*
    If you use the wizard to add a second appliance to the first appliance and the root password contains a comma (,), a backslash (\), or a space between two valid characters, the password breaks the install command causing the process to time out.

    Workaround: Do not use a comma (,), a backslash (\), or a space between two valid characters in the root password while deploying the vRealize Automation appliance for the first time.

  • If you create a property group with a period in the group name, you cannot use the vRealize Automation user interface to edit the group*
    This issue occurs when you create a property group with a period in the group name, for example, property.group. If you use the vRealize Automation user interface to edit this property group, a blank page appears. You can use the REST API to edit this property group.

    Workaround: Avoid using a property group name that contains a period. If that is unavoidable, use the REST API to edit the group.

  • Loss of communication between IaaS and the common service catalog during destroy process leaves virtual machine in a disposing state*
    If communication is lost between IaaS and the common service catalog while the destroy request is in progress but before vRealize Automation removes the virtual machine record from the database, the machine remains in a disposing state. After communication is restored, the destroy request is updated to either successful or failed, but the machine is still visible. Although the machine is deleted from the endpoint, the name remains visible in vRealize Automation management interface.

  • The Destroy VMware NSX load balancer option appears as an entitled action or as an approval policy option*
    Permission to destroy the VMware NSX load balancer incorrectly appears as an entitled action and as an approval policy option on the Administration tab. The option to destroy the load balancer is correctly hidden from the list of actions on the provisioned load balancer resource, but remains visible on the Administration tab. Although the options are present, they are nonfunctional.

  • Edge fails to allocate virtual machine when network custom property is specified at the blueprint level*
    When you use a custom property to specify a connection to an external network in a blueprint for a virtual machine, a machine request is unsuccessful and generates an error message similar to the following: Infrastructure service provider error: A server error was encountered. Error requesting machine. IP Address: 10.10.10.1 is not available for the network profile external-network-profile.

    Workaround: Use a custom property at the machine level rather than at the blueprint level to specify the connection to the external network.

  • When you change the vRealize Automation appliance host name, services are marked as unavailable

    Workaround: If any services are unavailable after you change the host name, restart the vRealize Automation server.

  • When you join a Management Agent domain account on a cloned Windows Server 2012 to a domain, the Management Agent domain account loses its rights on the agent certificate private key
    When you use a customization wizard to clone a machine in vSphere that is part of a domain, the machine is no longer part of that domain. When you rejoin the cloned machine to the domain, the following error message appears in the Management Agent log: CryptographicException - Keyset does not exist.

    Workaround: Resolve this issue use the following procedure to open and close the security settings for the private key of the certificate without making any changes.

    1. Locate the certificate by using the Microsoft Management Console Certificates snap-in. The snap-in displays the agent ID in its Friendly name text box.
    2. Select All Tasks > Manage Private Keys.
    3. Click Advanced.
    4. Click OK.

  • Dragging an existing inner blueprint into a current outer blueprint is restricted
    When you drag an existing inner blueprint into a current outer blueprint, the following restrictions apply if the inner blueprint has machines joined to security groups, security tags, or on-demand networks. This issue might also occur on imported blueprints.
    • The outer blueprint cannot contain an inner blueprint that contains on-demand network settings or on-demand load balancer settings. Using an inner blueprint that contains an NSX on-demand network component or on-demand load balancer component is unavailable..
    • When you add new or additional security groups to machines in the inner blueprint, the machines are joined only to new security groups that are added as part of an outer blueprint, even though the Blueprint Authoring page shows security groups from the inner and outer blueprint.
    • When you add new security tags to inner machines from an outer blueprint, security tags originally associated in the inner blueprint are no longer available.
    • When you add new on-demand networks to inner machines from an outer blueprint, on-demand networks originally associated in the inner blueprint are no longer available. Existing networks originally associated in inner blueprint remain available.

    Workaround: You can resolve this issue by performing oneof the following tasks:

    • Add security groups, tags, or on-demand networks to the outer blueprint but not to the inner blueprint.
    • Add security groups, tags, or existing networks to the inner blueprint but not in the outer blueprint.

  • Directory Search Attribute menu on the Add Directory page contains inaccurate information
    Some code strings that first appear in the Directory Search Attribute menu are inaccurate.

    Workaround: Click the Directory Search Attribute drop-down menu to view accurate code strings.

  • Resource not found error occurs when requesting a catalog item
    When vRealize Automation is in High Availabity mode, if the master database node fails and a new master node is not promoted, all of the services that require write access to the database fail or become temporarily corrupted until a new master database is promoted.

    Workaround: You cannot avoid this error when the master database is unavailable. You can promote a new master database so that this error disappears and you are able to request resources.

  • Changes are not saved on the Blueprint Form page of an XaaS blueprint
    If you do not click Apply after you update each field on the Blueprint Form page of an XaaS blueprint, your changes are not saved.

  • In vRealize Automation 7.0, custom property names are case-sensitive
    In earlier versions of vRealize Automation, custom property names are case-insensitive. In 7.0, custom property names must be an exact match, including the case. This change ensures that property values override one another and match property dictionary definitions. For example, two properties hostname and HOSTNAME are considered different properties by vRealize Automation 7.0 and would not override one another.

  • Items tab does not display information about the services that are enabled for a load balancer
    For machines provisioned by using a load balancer that is associated with vCloud Networking and Security, the Items tab does not display information about the services that are enabled for that load balancer.

  • If a machine is destroyed while vSphere clone operation is in progress, the in-progress machine clone task is not canceled
    This issue might cause the machine to be cloned. The cloned virtual machine might be managed in vCenter and no longer be under vRealize Automation management.

  • When you request a composite blueprint, the request fails immediately and the request details form fails to load
    When the maximum lease days for a component blueprint are less than the number of lease days in the outer blueprint, requests fail immediately and the request details form fails to load.

  • You cannot have deployments with bindings to DHCP IP addresses in software deployments
    If you attempt to do this, the ip_address is not available if no network profile exists. The following error message appears: System error: Internal error in processing component request: com.vmware.vcac.platform.content.exceptions.EvaluationException: No data for field: ip_address.

    Workaround: If a binding is required, use static IP addresses or IP addresses managed by vRealize Automation in the network profile, or use an IPAM integration. If you use DHCP, you should bind to the host name and not to the IP address.

    You can use the following script to get the IP address of a Cent OS machine:
    IPv4_Address = $(hostname -I | sed -e 's/[[:space:]]*$//')
    echo $IPv4_Address

    Bind to the value this scrip provides when the IP address is needed for DHCP use cases.

  • Domain is added to a user UPN when you create a directory that includes the UserPrincipalName directory search attribute
    When you create a new directory and you select UserPrincipalName for the Directory Search Attribute, a domain is added to a user UPN. For example, the vRealize Automation user name of a user with user.domain@domain.local UPN appears as user.domain@domain.local@domain.local. This happens if the UPN suffix is configured at AD site to be domain. If the UPN suffix is customized, for example to "example.com,"then the vRealize Automation user name of a user with user.domain@example.com UPN appears as user.domain@example.com@domain.local.
    If UserPrincipalName directory search attribute is used, users must enter their user name exactly as it appears (user.domain@domain.local@domain.local), including the domain, to log in to use the REST API or Cloud Client.

    Workaround: Use sAMAccountName instead of UserPrincipalName to use the user name domain uniqueness functionality of Directories Management.

  • A 404 Not Found error appears when requesting a machine on behalf of another user
    If a blueprint includes an on-demand NAT network or an on-demand load-balancer component, a 404 Not Found error appears when a deployment requested on behalf of another user is made.

  • Machines imported with Bulk Import are not mapped to the correct converged blueprint and component blueprint

    Workaround: Add the VMware.VirtualCenter.OperatingSystem custom property to each machine in the import CSV file.

    For example:
    Yes,NNNNP2-0105,8ba90c35-9e03-4ac4-8a5d-2e6d76f37b81,development-res,ce-san-1:custom-nfs-2,UNNAMED_DEPLOYMENT-0105,BulkImport,Imported_Machine,system_blueprint_vsphere,user.admin@sqa.local,VMWare.VirtualCenter.OperatingSystem,sles11_64Guest,NOP

  • Catalog Management Actions are missing in vRealize Automation

    Workaround: For information on how to resolve this issue, see Knowledge Base 2113027.

  • An Active Directory that includes more than 15 user groups fails to list the groups when you sync the Active Directory
    If you have more than 15 groups, and you attempt to synchronize the Active Directory in the vRealize Automation management interface using Administration > Identity Stores Management > Identity Stores, only a few groups appear.

    Workaround: Click Select to view the full list.

  • After you promote a replica instance to the master instance, wrong information appears on the Database tab in the vRealize Automation master node management interface
    When the master node in the vRealize Automation appliance fails, you should use the vRealize Automation appliance management interface of a healthy node for cluster management operations.

  • Moving a datastore from one vSphere Storage DRS to another causes the system to delete instead of create a virtual machine*
    If you move a datastore from one vSphere Storage DRS cluster to another vSphere Storage DRS cluster and the target cluster's automation level is not automatic, reprovisioning a created machine causes the system to delete the machine with the following error: StoragePlacement: datastore unspecified for disk in sdrs-disabled VM. This issue does not occur if the virtual machine is cloned.

    Workaround: Verify that the target cluster's automation level is set to automatic before you move a datastore from one vSphere Storage DRS cluster to another.