VMware Cloud Community
gradinka
VMware Employee
VMware Employee

vRA 7.4 cumulative hotfix #5 (HF5) is now available

vmware kb 56618

Resolved Issues

Symptoms (or related KB Article)

Patched in HF ReleaseResolved in Version

Missing request schemas for machine day-2 operations create-snapshot and change-lease.

An HTTP error, 404 (Not Found) is returned, instead of a valid schema, when using the vRA REST API to obtain the request schemas for the machine-level, day-2 operations, "Change Lease" and "Create Snapshot".
REST API in question:

https://{{VA}}/catalog-service/api/consumer/resources/{{RESOURCE_ID}}/actions/{{DAY_2_ACTION_ID}}/requests/schema

where VA is the vRA URL, RESOURCE_ID is the vRA identifier for the machine and DAY_2_ACTION_ID is the vRA identifier for either the "Change Lease" or "Create Snapshot" machine-level, day-2 operation.

This issue will not affect users using vRA via the vRA UI. Only REST API users are affected.

HF57.5

ASD creates two duplicate workflow items for same request.

A XaaS blueprint with user interaction sometimes results with two manual user actions instead of one. The issue only appears in HA environment.
Reason: Synchronization problem between the nodes.

Workaround: Switch to single node environment

HF57.5

vCenter new machine name cannot be found in items search page.

If the machine name is changed directly on vCenter then a state data collection is run right after, then the new name appears in the items page but cannot be found via search. 

Exception:
If the state data collection was run after the machine name changed at the endpoint, but before the hotfix was applied, the new name will not appear in the items search page.

Workaround: After the fix is applied, change the machine name again in the vCenter endpoint, run state data collection. Confirm that the new name appears in the items search page. Then change the machine name again to the desired name at the vCenter endpoint. Run state data collection. Now the desired name will appear on the items search page.

HF57.5

Capacity alert emails are not sent.

Capacity alert emails are not sent.

HF57.5

When adding multiple disks during reconfigure operation, of day 2 operation, "xxxxx.vmdk already exists" error returns if reservation is on a single datastore (No SDRS is used in reservation).

Error message:
 
"Reconfigure virtual machine [virtual machine name]. Cannot complete the operation because the file or folder [data store] xxxxxxxx_x.vmdk already exists"

HF57.5

Switching between form pages can be slow when a workflow is created with many inter-field dependencies and custom validations for workflow inputs.

This behavior is caused by excessive custom validation of workflow inputs.
 
Removing the custom validations of the workflow inputs significantly speeds up the switching between form pages.
 
The the execution of custom validations will be disabled when next page button is pressed. The custom validations will still be executed when Submit button is pressed. When a field value is modified, custom validations for that field will also be executed, but for that field only.

HF5TBD

Provisioning fails when deploying an OVF template with additional disks to an SDRS cluster.

If a blueprint component uses the ImportOvfWorkflow, and at least one additional disk has been added to to it, provisioning will fail with a message similar to the following, if the VM is allocated to an SDRS cluster:
 
[ReconfigVM_Task] - Invalid datastore path 'vmname/vmname_1.vmdk'
 
Exception: If the Agent is added after the hotfix is applied, and the new agent is used for ova deployment, additional manual changes will need to be made to the agent, please contact GSS.

HF57.5

vIDM performance enhancements.

- Improvements to synch calls to ehcache

- Improvements to directory sync

HF57.5

NSX deployed items periodically show up as virtual machines and not NSX items.

NSX deployed items periodically show up as virtual machines and not NSX items

HF57.5

Resiliency improvements for vRA database clustering.

Resiliency improvements for vRA database clustering in 3VA / "SYNC" mode
https://kb.vmware.com/s/article/52018

HF57.5

Date picker on custom form cannot be associated to a custom property.

Date picker on custom form cannot be associated to a custom property

HF57.5

All provisioning requests for specific vRA Business Groups are failing with status "The Request approval has returned with an Error".

In the catalina.out log you will see errors similar to:

    2018-03-05 11:56:38,452 vcac: [component="cafe:identity" priority="ERROR" thread="tomcat-http--17" tenant="vsphere.local" context="XSGpJEf4" parent="3MIaKWAr" token="pTyxM34b"] com.vmware.vcac.authentication.service.impl.PrincipalWrapperFactoryImpl.create:60 - Could not find principal 'testDelete@vsphere.local' in tenant 'vsphere.local'

    2018-03-05 11:56:38,498 vcac: [component="cafe:approvals" priority="INFO" thread="queue-pool-executer-2" tenant="" context="XSGpJEf4" parent="XJxiYUAr" token="Ik6k65RA"] com.vmware.vcac.core.approvals.service.evaluation.DefaultPrincipalResolver.convertToPrincipals:168 - The value of field path organization.subTenant~ROLE_CSP_SUBTENANT_MANAGER returned by the provider is null

Pre-HF57.5

Directory sync stops working after upgrading to vRealize Automation 7.4.

https://kb.vmware.com/s/article/56193

Pre-HF57.5

Deploying OVF/OVA Blueprint fails to apply property values where the property name contains uppercase characters.

When deploying an OVF/OVA template that contains user-configurable OVF properties, the property values specified by the requestor are not applied to the resulting virtual machine. You might notice that instead of the specified values being applied, the default values defined in the OVF template itself are applied.

Pre-HF57.5

Duplicate property causing SQL 2014 installer to crash.

When deploying SQL Server 2014 you may encounter errors such as "Property loading failed.  Duplicate property '<property here>' found.  Ignoring the property.

Pre-HF57.5

After upgrading to vRealize Automation from 7.3 to 7.4 /usr/lib/vcac fills up with Java dump files (.hprof).

https://kb.vmware.com/s/article/55095

Pre-HF57.5

API needs to prevent custom properties from being updated during reprovision.

In some cases, hidden custom properties can become visible upon reprovision requests.

Pre-HF57.5

Unable to start Xenon service after upgrading to vRA 7.4.

https://kb.vmware.com/s/article/55649

Pre-HF57.5

Schema doesn't load for Machine lifecycle and Machine provisioning event topics in vRA subscription.

https://kb.vmware.com/s/article/55837

Pre-HF57.5
0 Kudos
2 Replies
agbiront
Contributor
Contributor

I had HF4 installed, and found out at VMworld that it was rolled back. When I came back y searched the KB article for HF4 and it pointed to the HF3 patch. No statement, no info, not a single thing describing why the HF4 was not available anymore and what was wrong with it...

0 Kudos
gradinka
VMware Employee
VMware Employee

there were issues around size (very big) and installation (for some customers) with HF4.


this one (HF5) is cumulative - it includes everything that HF4 had + more,
and of course the above mentioned issues rectified.

0 Kudos