Upgrading Tanzu Application Service fails with Unexpected EOF during uploading releases

Products

• VMware Tanzu Application Service

Issue/Introduction

When upgrading from TAS. In this example we are upgrading from v4.0.32LTS to v6.0.12. Upgrade/Deployment fails with the following error:

Release 'uaa/77.20.2' for stemcell 'ubuntu-jammy/1.719' already exists.
Creating and uploading releases:
 - Uploading release 'java-native-image-cnb-buildpack/0.11.22':
     Extracting release:
       Shelling out to tar:
         Running command: 'tar --no-same-owner -xzf /var/tempest/releases/java-native-image-cnb-buildpack-0.11.22-ubuntu-jammy-1.719.tgz -C /home/tempest-web/.bosh/tmp/bosh-release1881364088', stdout: '', stderr: '
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

 

 

Cause

The error

gzip: stdin: unexpected end of filetar: Unexpected EOF in archive
tar: Unexpected EOF in archive

is related to the file that was uploaded, More data is expected but suddenly it has reached end of file. The file might be corrupted or might be due to incomplete upload.

 

 

Resolution

A workaround it to upload the corrupted release.

1. Download the TAS installer

2. Uncompress TAS installer and locate the corrupted release under release folder. In this example the corrupted release is java-native-image-cnb-buildpack-0.11.22-ubuntu-jammy-1.719
3. Once located use sample command below:

bosh upload-release <path>/java-native-image-cnb-buildpack-0.11.22-ubuntu-jammy-1.719 --fix

3. Retry with the upgrade.

You might need to repeat steps 1 to 4 if there are more corrupted releases.