7.0.1
Table Of Contents
- Upgrading from vRealize Automation 7.0 to 7.0.1
- Contents
- Updated Information
- Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Reconfigure External Workflow Timeouts
- Verify That vRealize Orchestrator Service is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Configure an External PostgreSQL Database to Merge into an Embedded PostgreSQL Environment
- Ensure Deployed Virtual Machines Register With Software Service
- Restore Changes to Logging
- Troubleshooting the Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- 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
Cause
During runtime, the manager service fails to run due to SSL validation errors.
Solution
1 Open the ManagerService.config configuration file.
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 an upgrade to vRealize Automation 7.0.1, unsynchronized user accounts are denied access 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 definitions from prior versions appear in the service catalog but
are not available to request after upgrading to vRealize Automation 7.0.1.
Problem
If you upgraded from a 6.2.x or earlier version and you had property definitions with the following control
types or attributes, the attributes are missing from the property definitions and any catalog items that use
the definitions do not function the way that they did before upgrading .
n n
Control types. Check box or link.
n
Attributes. Relationship, regular expressions, or property layouts.
Cause
Beginning in vRealize Automation 7.0, the property definitions no longer use the attributes. You must
recreate the property definition or configure the property definition to use avRealize Orchestrator script
action rather than the embedded control types or attributes.
In vRealize Automation 7.0 and later, the property definitions no longer use the attributes. You must
recreate the property definition or configure the property definition to use a vRealize Orchestrator script
action rather than the embedded control types or attributes.
Migrate the control type or attributes to vRealize Automation 7.0 using a script action.
Upgrading from vRealize Automation 7.0 to 7.0.1
VMware, Inc. 37