"Synchronizing reservations and reservation policies: Failed" error while migrating from vRA 6.2.x to 7.x

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

Migration from vRealize Automation 6.2.x to 7.x fails, you see these symptoms:

• Unable to synchronizing the IaaS reservation entities from the IaaS database to the CAFE database.
• In the IaaS migration log located at <drive>:\Program Files (x86)\VMware\vCAC\InstallLogs-<timestamp>\migrate.log file, you see entries similar to:
  
  Synchronizing reservations failed. Error: [DynamicOps.Common.Client.HtmlResponseException: (500)
  Request:
  POST https://{vra-fqdn}/reservation-service/api/reservations/sync/com.vmware.csp.iaas.blueprint.service/?page=1&limit=200
  Response:
  {"errors":[{"code":50505,"message":"System exception.","systemMessage":"I/O error on GET request for \" https://{vra-fqdn}/iaas-proxy-provider/api/services/<UUID>/reservations/?page=1&limit=200\ ":
  Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out","moreInfoUrl":null}]}
  at VMware.Cafe.ReservationClient.BatchSyncInternal(Uri resource)
  at VMware.Cafe.ReservationClient.SyncReservations(Int32 startPage, Int32 pageSize)
  at VMware.Cafe.Client.Synchronization.SynchronizeReservation(Action`1 logMessage, Int32 startPage, Boolean verbose)]
  Database synchronization [Reservation] finished at 03/30/2017 21:39:41.
  Warning: Non-zero return code. Command failed.
  
  Synchronize reservations and reservation policies: Failed

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vRealize Automation 6.x
VMware vRealize Automation 7.x

Cause

This error occurs because of a time out being hit due to a large amount of reservation data being synchronized from the IaaS repository to the vRealize Automation appliance repository when running the following command on the vRealize Automation Model Manager Data node during the migration process:

drive-letter:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" SynchronizeDatabases -dst Reservation,ReservationPolicy -v


 

Resolution

If a migration to vRA 7.x fails because of a timeout during migration of Reservations, follow the below steps:

1. On the vRA virtual appliance, add the following lines to /etc/vcac/vcac.properties

reservation.sync.page.size.default=20
reservation.sync.page.size.max=50

2. ​Restart the primary vRA service:

service vcac-server restart

3. ​Start the migration process again.
4. Check the reservations migration process within the log file:

/var/log/vmware/vcac/va-migration.log