When users upgrade TAS to version 4.0.24 on AWS and they have the VM size set to automatic with default parameter they will notice that it fails when upgrading the cloud controller VM.
Customer will see an error similar to:
Task 10000 | 09:06:23 | Updating instance cloud_controller: cloud_controller/xxxx-xxxx-xxxxx (0) (canary) (00:03:29)
L Error: Action Failed get_task: Task xxx-xxxx-xxxxx-xxxx result: Preparing apply spec: Preparing package ruby-buildpack-cflinuxfs3: Installing package directory: Decompressing package files: Shelling out to tar: Running command: 'tar --no-same-owner -xzf /var/vcap/data/tmp/bosh-http-blob-provider-GET3820162907 -C /var/vcap/data/packages/ruby-buildpack-cflinuxfs3/xxxxxxxxxxxxxxxxxxxxxxx, stdout: '', stderr: 'tar: ./ruby_buildpack-cached-cflinuxfs3-v1.10.15.zip: Wrote only 3072 of 10240 bytes
tar: Exiting with failure status due to previous errors
': exit status 2
Preparing package php-buildpack-cflinuxfs3: Installing package directory: Decompressing package files: Shelling out to tar: Running command: 'tar --no-same-owner -xzf /var/vcap/data/tmp/bosh-http-blob-provider-GET2514229768 -C /var/vcap/data/packages/php-buildpack-cflinuxfs3/87f5328c44dbdb020673f1b7b5b2714af3ea773c', stdout: '', stderr: 'tar: ./php_buildpack-cached-cflinuxfs3-v4.6.19.zip: Wrote only 5120 of 10240 bytes
tar: Exiting with failure status due to previous errors
': exit status 2
Upgrading Tanzu Application services for VMs to version 4.0.24
This issue is caused because of the increase of the size of the buildpacks needed by the platform.
In order to workaround the issue, an upgrade on the VM size in order to have a bigger disk is required for the update.
After the update the VM size can be reduced.
R&D team is working to change the default VM size to one with a 40GB disk for the CC VM.