Failure attaching foundation to Tanzu Hub in air-gapped environment: "tas-hub-collector-10.4.0 has unexpected status FAILED"
search cancel

Failure attaching foundation to Tanzu Hub in air-gapped environment: "tas-hub-collector-10.4.0 has unexpected status FAILED"

book

Article ID: 439744

calendar_today

Updated On:

Products

VMware Tanzu Platform - Hub

Issue/Introduction

  • Tanzu Hub 10.4 installed in an air-gapped environment might encounter errors when attaching foundations.
  • This occurs after using cf CLI to manually download the necessary product capabilities as detailed in the Tanzu cf CLI commands for air-gapped environments documentation.
    • SPECIFICALLY, this issue occurs following the manual corrective action prescribed in this KB, when the TtlSeconds limit is exceeded and products are remove from Tanzu Hub.
  • When attaching foundations after the tas-hub-collector-10.4.0 product has been timed out and removed from Hub, the error: "Capabilities download workflow warehouse-release-download-################################-tas-hub-collector-10.4.0 has unexpected status FAILED" is returned during the attach workflow in Tanzu HUB GUI.

Environment

Tanzu Hub 10.4 air-gapped.

Cause

This failure occurs because the hubDocumentServiceTtlSeconds value set in the download manifest file during Step 2 of this KB has been reached. When this timeout value is reached, Hub automatically removes the products that were manually uploaded, leading to the failure in download workflow during attach operations. Step 2 of the reference KB notes this:

NOTE: The TtlSeconds hubDocumentServiceTtlSeconds: 2628000 configures this to hold the product for 30 days in Tanzu Hub. These products will be automatically removed from Hub and will require this manual process be run again if the TtlSeconds expire.

Resolution

This is resolved in the first patch release of Tanzu Hub: 10.4.1 with the ability to use Proxy for automatic product-warehouse download.

 

Workaround

Run the Manual download and upload of the desired products again using the steps detailed in this KB.