VMware vRealize Automation 7.3.1 is now available

[gradinka]

VMware vRealize Automation 7.3.1 is now available

Whats New?

• This release contains resolutions for 73+ issues reported on .vRealize Automation 7.2 and 7.3, as well as multiple security updates
  For more information, see Resolved Issues.

Documentation and Links:

• RNs: https://docs.vmware.com/en/vRealize-Automation/7.3/rn/vRealize-Automation-731.html
• Download URL: https://my.vmware.com/group/vmware/details?downloadGroup=VRA-731&productId=650&rPId=21641

[nsajepi]

Thank you very much for sharing this.

[rmav01]

We just upgraded from 7.2 to 7.3.1 in our lab environment. It blasted away several endpoints, and this didn't fix it:

VMware Knowledge Base

[rmav01]

We just upgraded from 7.2 to 7.3.1 in our lab environment. It blasted away several endpoints, and this didn't fix it:

VMware Knowledge Base

FYI to anyone that runs into this. The endpoints it killed were ones set with priorities. My colleague reverted back to 7.2 via backup, and removed the priority settings on these endpoints and it fixed it the 2nd upgrade attempt. Luckily it was a small environment so that we could do this kind of retry. Just a heads up to those of you working on enterprise deployments, and perhaps to VMware to fix this issue.

[gradinka]

Hi - I've pinged you with a request abt more details around that

[nsb24]

When you say "The endpoints it killed were ones set with priorities". Where are the priorities set on the endpoints in 7.2? Is it vCenter endpoint or some custom endpoint?

[nsb24]

Did you have any sort of custom property in vCenter endpoint in 7.2? e.g. "VMware.VCenterOrchestrator.Priority" set in vCenter endpoint, if so then this property should not exist on the vCenter endpoint. So deleting the property is a correct workaround. Also there is no such priority field for vCenter endpoint, AFAIK. The priority only exists for vRO endpoints.