Skip to main content
NetApp Knowledge Base

Cloud Sync fails with "Could not refresh access token: Request failed with status code 403"

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

Applies to

  • Cloud Sync
  • Proxy

Issue

  • When sync is started it fails in INITIALIZE step with error "Could not refresh access token: Request failed with status code 403"
  • Data Broker logs:
[INFO] [MASTER] [0] [12833] Handling copy message 
[INFO] [MASTER] [0] [12833] Vault mode is enabled, getting credentials from vault 
[INFO] [MASTER] [0] [12833] Vault is initialized and unsealed 
[INFO] [MASTER] [0] [12833] SEND MESSAGE: {"message":{"step":"INITIALIZE","relationshipId":"6xxxxxxxxxxxxxx","status":"FAILED","reason":"Could not refresh access token: Request failed with status code 403","source":{"gcp":{"path":"data/xxx/xxx","bucket":"data","tags":[],"storageClass":"STANDARD"}},"target":{"s3":{"bucket":"prod","tags":[],"provider":"s3","path":"prod","encryption":{"kms":{"keyId":"xxxx-xxxx-xxxx-xxxxx"}},"region":"ap-southeast-2"}},

 

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.