Pre-requisites for upgrading or migrating from vRealize Automation 6.2.x to 7.x
Article ID: 343008
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article provides the KB article information for different known issues encountered after upgrading or migrating from vRealize Automation 6.2.x to 7.x.
Environment
VMware vRealize Automation 7.2.x
VMware vRealize Automation 7.4.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 7.4.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 7.3.x
Resolution
Below are the KB articles to be followed as a Pre-requisite before Upgrading or Migrating from vRealize Automation 6.2.x to 7.x :
Note: KB 2150759 and 51096 are not applicable for vRealize Automation 7.3.1, these are for only 7.3. KB 2150515 is still valid and to be applied to the 6.2.x system prior to upgrading to 7.x.
| Problem Description | Type | KB Article |
|---|---|---|
| Virtual machines do not appear in the Items page after upgrading from vRA Automation 6.2.x to 7.x | Migration / Upgrade to 7.x | 2150515 |
| Virtual machines show their blueprint component to be unassigned after upgrade or migration from vRealize Automation 6.2.x to 7.3 | Migration / Upgrade to 7.3 | 2150759 |
| Migration from vRA 6.2.x to vRA 7.2 or 7.3 leaves a large number of mismatched and empty resources in Deployments or fails with "504 Gateway time-out" or "413 Request Entity Too Large" errors | Migration to 7.2 or 7.3 | 51096 |
Note: KB 2150759 and 51096 are not applicable for vRealize Automation 7.3.1, these are for only 7.3. KB 2150515 is still valid and to be applied to the 6.2.x system prior to upgrading to 7.x.
Feedback
Yes
No
Powered by
