Search the VMware Knowledge Base (KB)
View by Article ID

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

  • 1 Ratings

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/f8d54a24-ed6c-46f6-bf21-c82d503c7af8/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.

Cause

This error occurs because of a time out, which is configured on the vRealize Automation CAFE appliance that is executing the migration, being hit due to a large amount of reservation data being synchronized from the IaaS repository to the CAFE 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

To resolve the issue, extend the timeout on the vRealize Automation 7.x appliance.

To extend the timeout on the vRealize Automation 7.x appliance:

  1. Log in to the master vRealize Automation 7.x appliance using root credentials.
  2. Open the /etc/vcac/setenv-user file using a text editor.
  3. Add the line to the file:

    VCAC_OPTS="$VCAC_OPTS -Dclient.system.socket.timeout=300000"

  4. Save and close the setenv-user file.
  5. Restart the vcac-server service by running the command:

    service vcac-server restart

Note: The timeout is set to 300000 which equates to 5 minutes. You can extend this timeout if required but if you are using a load balancer, you must ensure that any load balancer's timeout should not forcibly close the connection as some load balancers close connections after 5 minutes. If you are not sure whether your load balancer has a connection time out configured, you can bypass the load balancer for the duration of the migration by pointing your vRealize Automation Load Balancer FQDN DNS record to the IP address of the master vRealize Automation node that you executed the migration on. After migration completes, you can revert and repoint your DNS records back to the IP address of your load balancer service.



Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: