Workload fails to be deployed with error message "error requesting remote resource: resolution took longer than global timeout of 1m0s"
search cancel

Workload fails to be deployed with error message "error requesting remote resource: resolution took longer than global timeout of 1m0s"

book

Article ID: 394557

calendar_today

Updated On:

Products

VMware Tanzu Application Platform

Issue/Introduction

Workload deployment failed on config-writer with an error message - error requesting remote resource: resolution took longer than global timeout of 1m0s

$ tanzu apps workload get -n NAMESPACE WORKLOAD-NAME
? Overview
   name:        WORKLOAD-NAME
   type:        web
   namespace:   NAMESPACE

? Source
   type:       git
   url:        SOME-URL
   branch:     SOME-BRANCH
   revision:   SHOME-SHA

? Supply Chain
   name:   SUPPLY-CHAIN-NAME

   NAME               READY   HEALTHY   UPDATED   RESOURCE
   source-provider    True    True      20d       gitrepositories.source.toolkit.fluxcd.io/WORKLOAD-NAME
   image-provider     True    True      23m       images.kpack.io/WORKLOAD-NAME
   config-provider    True    True      8d        podintents.conventions.carto.run/WORKLOAD-NAME
   app-config         True    True      8d        configmaps/WORKLOAD-NAME
   service-bindings   True    True      8d        configmaps/WORKLOAD-NAME-with-claims
   api-descriptors    True    True      8d        configmaps/WORKLOAD-NAME-with-api-descriptors
   config-writer      False   False     11m       taskruns.tekton.dev/WORKLOAD-NAME-config-writer-vknzg
   deliverable        True    True      120d      configmaps/WORKLOAD-NAME-deliverable

? Delivery

   Delivery resources not found.

? Messages
   Workload [HealthyConditionRule]:   error requesting remote resource: resolution took longer than global timeout of 1m0s

Cause

The tekton deprecated cluster tasks and pushed users to a similar looking solution, cluster resolvers. But cluster resolvers are slow and have a hard coded timeout of 1 minute. 

Resolution

Temporary workaround

Deleting the failing taskrun or redeploying the workload. Deletion of the taskrun is suggested.

Permanent fix 

This issue is expected to be fixed in Tanzu Application Platform (TAP) v1.12.3. Please contact the Tanzu support team if you need any additional information or explanation.