Skip to main content
NetApp Knowledge Base

Cloud sync fails to sync with error "Request failed with status code 503"

  1. Last updated
  2. Save as PDF
Views:
142
Visibility:
Public
Votes:
2
Category:
cloud-sync
Specialty:
bluexp
Last Updated:

Applies to

  • Cloud sync
  • External HashiCorp Vault

Issue

  • Cloud sync fails to sync with error "Request failed with status code 503" when trying to get the credentials from External Vault
  • Data Broker logs :
[INFO] [MASTER] [0] [2723] Vault mode is enabled, getting credentials from vault
[DEBUG] [MASTER] [0] [2723] Booting Vault mode
[DEBUG] [MASTER] [0] [2723] Login with role, secret and namespace: { VAULT_ROLE_ID: 'xxxxx-xxxx-xxxx-xxxx', VAULT_NAMESPACE: 'vault_cloudsync' }
[INFO] [MASTER] [0] [2723] SEND MESSAGE: {"message":{"step":"INITIALIZE","relationshipId":"xxxxxxxxxxxxxxx","status":"FAILED","reason":"Request failed with status code 503","source":{"cifs":{"host":"10.xx.xx.xx","share":"QA","version":"3.0","provider":"cifs","path":"test"}},"target":{"nfs":{"host":"xxxxxxxxxx","export":"/","version":"4.1","path":"/qa/test","provider":"efs","accessPoint":"fsap-xxxxxxxxxxxx"}}

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.