DMS - provider configuration - Object Storage Repositories setup failed with "Forbidden status code: 403"
search cancel

DMS - provider configuration - Object Storage Repositories setup failed with "Forbidden status code: 403"

book

Article ID: 297283

calendar_today

Updated On:

Products

VMware Data Services Manager

Issue/Introduction

When configure the provider, there is one step to configure the "Object Storage Repositories". This configuration only requires update the "Tanzu Net Token" and "Storage setting" in Settings. After provide the correct setting for these two items,  provider will automatically start the "release process" in "operations". 

This operation may fail with below error: 
com.vmware.tdm.sp.common.exception.TdmException: Error Processing template tasks 
at com.vmware.tdm.sp.release.services.TanzuNetReleaseProcessor.startDownloadAndUploadTemplates(TanzuNetReleaseProcessor.java:320)
at com.vmware.tdm.sp.release.services.TanzuNetReleaseProcessor.loadTanzuNetRelease(TanzuNetReleaseProcessor.java:150)
at com.vmware.tdm.sp.release.services.TanzuNetReleaseProcessor$$FastClassBySpringCGLIB$$9f0bbee2.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:367)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:88)
at com.vmware.tdm.sp.configuration.aop.DataSourceRouteInterceptor.proceed(DataSourceRouteInterceptor.java:34)
at jdk.internal.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644)
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:633)
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
at com.vmware.tdm.sp.release.services.TanzuNetReleaseProcessor$$EnhancerBySpringCGLIB$$dca72f8f.loadTanzuNetRelease()
at com.vmware.tdm.sp.release.services.ReleaseProcessor.loadRelease(ReleaseProcessor.java:122)
at com.vmware.tdm.sp.release.services.ReleaseProcessor$$FastClassBySpringCGLIB$$8f86161.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.ExecutionException: com.vmware.tdm.sp.common.exception.TdmException: Forbidden: Forbidden
status code: 403, request id: , host id: 
at java.base/java.util.concurrent.FutureTask.report(Unknown Source)
at java.base/java.util.concurrent.FutureTask.get(Unknown Source)
at com.vmware.tdm.sp.release.services.TanzuNetReleaseProcessor.startDownloadAndUploadTemplates(TanzuNetReleaseProcessor.java:316)
... 37 more
Caused by: com.vmware.tdm.sp.common.exception.TdmException: Forbidden: Forbidden
status code: 403, request id: , host id: 
at com.vmware.tdm.sp.template.tasks.TanzuNetDownloadAndUploadTask.uploadTemplate(TanzuNetDownloadAndUploadTask.java:98)
at com.vmware.tdm.sp.template.tasks.TanzuNetDownloadAndUploadTask.downloadAndUploadTemplates(TanzuNetDownloadAndUploadTask.java:64)
at com.vmware.tdm.sp.template.tasks.TanzuNetDownloadAndUploadTask.call(TanzuNetDownloadAndUploadTask.java:46)
at com.vmware.tdm.sp.template.tasks.TanzuNetDownloadAndUploadTask.call(TanzuNetDownloadAndUploadTask.java:31)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
... 1 more


Environment

Product Version: 1.4

Resolution

Although this error "Forbidden status code: 403" normally means an incorrect setting at the storage server side, or something related storage setting. The actual reason is due to NTP service not working properly. After corrected NTP service on the previously designated NTP server. The release processing can complete ok.

Powered by Wolken Software