Pipeline fails to download vSphere Xenial Stemcell 621.151 from Tanzu Network

Products

• Concourse for VMware Tanzu

Issue/Introduction

vSphere Xenial Stemcell 621.151 was pulled or taken down from Tanzu Network due to a known issue with persistent disks attachment, specifically, only the vSphere release was pulled. 

Due to the vSphere release being pulled from Tanzu Network, other IaaS types of the stemcell are available for consumption and may cause automation pipelines to fail due to missing vSphere IaaS type.

+ om download-product --config config/tas-2.10.yml --output-directory downloaded-product --stemcell-output-directory downloaded-stemcell --source pivnet
attempting to download the file product-files/elastic-runtime/cf-2.10.18-build.4.pivotal from source pivnet
Cleaning up cached artifacts in directory 'downloaded-product' with the glob 'cf-*.pivotal'
checking if "cf-2.10.17-build.13.pivotal" needs to cleaned up
cleaning up cached file: downloaded-product/cf-2.10.17-build.13.pivotal
Cleaning up cached artifacts in directory 'downloaded-product' with the glob '\[cf,*\]cf-*.pivotal'
checking if "cf-2.10.17-build.13.pivotal" needs to cleaned up
 10.27 GiB / 10.27 GiB [=========================================] 100.00% 1m50s
calculating sha sum for downloaded-product/cf-2.10.18-build.4.pivotal.partial
Downloading stemcell
2021/09/14 22:06:52 could not download stemcell: for product version 621.151: the glob 'bosh*vsphere*' matches no file
No stemcell identified for IaaS "vsphere" on Pivotal Network. Correct the `stemcell-iaas` option to match the IaaS portion of the stemcell filename, or remove the option.

This issue occurs when the config file used for om download-product is pointing to Tanzu Network to download the stemcell. This feature is configured in the download-product task.

Note: Downloading the stemcell when a product is downloaded is an optional field that is set in the config file for om download-product.

The error above is returned because the config file tas-2.10.yml is specifying the stemcell-iaas type as vSphere. As a result of this definition, the latest version of the stemcell is always downloaded.

The following is output from config file tas-2.10.yml:

---
pivnet-api-token: ((pivnet-token))
pivnet-file-glob: "cf-*.pivotal"
pivnet-product-slug: cf
product-version-regex: ^2\.10\..*$
stemcell-iaas: vsphere

Resolution

Until a vSphere release of Xenial Stemcell version 621.151 is made available on Tanzu Network, you will have to edit the config file used for om download-product --config CONFIG_FILE to remove the stemcell-iaas definition.

Note: In some cases, within your config file you may be defining the stemcell product and version instead of relying on the optional download feature. If so, you will need to modify your config file to specify stemcell product version and avoid using v621.151.

The following example shows how the config file for the stemcell would look like if you were using a stemcell config file for om download-product:

---
pivnet-api-token: token
pivnet-file-glob: "*vsphere*"       # must be quoted if starting with a *
pivnet-product-slug: stemcells-ubuntu-xenial

# Either product-version OR product-version-regex is required
# product-version-regex: ^250\..*$  # must not be quoted
product-version: "250.82"

# Optional
# pivnet-disable-ssl: true  # default - false
# blobstore-bucket: bucket  # if set, product files will have their slug and
                            # version prepended. Set if the product will
                            # ever be stored in a blobstore