7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not Available to Request
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
Manager Service Fails to Run Due to SSL Validation Errors During
Runtime
The manager service fails to run due to SSL validation errors.
Problem
The manager service fails with the following error message in the log:
[Info]: Thread-Id="6" - context="" token="" Failed to connect to the core database, will retry in
00:00:05, error details: A connection was successfully established with the server, but then an
error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate
chain was issued by an authority that is not trusted.)
Cause
During runtime, the manager service fails to run due to SSL validation errors.
Solution
1 Open the ManagerService.config conguration le.
2 Update Encrypt=False on the following line: <add name="vcac-repository"
providerName="System.Data.SqlClient" connectionString="Data Source=iaas-db.sqa.local;Initial
Catalog=vcac;Integrated Security=True;Pooling=True;Max Pool
Size=200;MultipleActiveResultSets=True;Connect Timeout=200, Encrypt=True" />.
Log In Fails After Upgrade
You must exit the browser and log in again after an upgrade for sessions that use unsynchronized user
accounts.
Problem
After you upgrade vRealize Automation, the system denies access to unsynchronized user accounts at login.
Solution
Exit the browser and relaunch vRealize Automation.
Catalog Items Appear in the Service Catalog But Are Not Available to
Request
Catalog items that use certain property denitions from prior versions appear in the service catalog but are
not available to request after upgrading to the latest version of vRealize Automation.
Problem
If you upgraded from a 6.2.x or earlier version and you had property denitions with the following control
types or aributes, the aributes are missing from the property denitions and any catalog items that use
the denitions do not function the way that they did before you performed the upgrade.
n
Control types. Check box or link.
n
Aributes. Relationship, regular expressions, or property layouts.
Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
60 VMware, Inc.