vRA 7.0.1 release note is helpful but let me dig a little deeper.
http://pubs.vmware.com/Release_Notes/en/vra/vrealize-automation-701-release-notes.html
Known Issues
- Certain blueprints cannot be fully upgraded due to failures in updating catalog resources*
Upgraded multi-machine blueprints that contain on-demand networks or load balancer settings might not be fully functional after you upgrade to vRealize Automation 7.x.Workaround: After you upgrade, delete and re-create the deployments associated with multi-machine blueprints. All associated NSX Edge cleanup work must be done in NSX.
Q.1 Is this applicable to the upgrade case from vRA 6 to vRA 7.0.0 (or vRA 7.0.0 --> 7.0.1)?
Q.2 When we upgrade vRA from 7.0.0 to 7.0.1, is it recommended for us to use vRealize Automation Upgrade Assistance Program ?
- When you delete a tenant that has a large number of groups, the process might time out*
When the system fails to delete a tenant completely because the process times out, do not run the delete process again. After the process times out, the remaining tenant data eventually triggers a delete routine that completes the process automatically.
Q.4 What types of group does this say? Business Group, Fabric group or Custom Group?
Q.5 How many groups is this issue occurred by? 10, 100, 1000 or more?
Q.6 Doesn't a large number of users occur this issue?
Thanks.