How to increase disk for bosh concourse deployment VMs

Products

• Concourse for VMware Tanzu

Issue/Introduction

Bosh deployed concourse deployment fails with No space left on device. Sample error below. The error is due to disk having no space left. 

Task 26983 | 03:50:54 | L executing post-start: worker/02a60538-1182-4ba6-b1cb-68a7838df2f9 (1)Updating deployment:
Expected task '26983' to succeed but state is 'error'
Exit code 1
(00:01:35)
Task 26983 | 03:50:55 | Error: Action Failed get_task: Task 0f5862bb-2cd4-459f-7adb-5f57c4ba3922 result: Preparing apply spec: Preparing package concourse: Installing package directory: Decompressing package files: Shelling out to tar: Running command: 'tar --no-same-owner -xzf /var/vcap/data/tmp/bosh-blobstore-externalBlobstore-Get4012624927 -C /var/vcap/data/packages/concourse/090d2293071b7c2f6c43c5b60c1a982cd64f90cf', stdout: '', stderr: 'tar: ./resource-types/semver/rootfs.tgz: Cannot write: No space left on device

To avoid this issue, we need to allocate more disk. 

Environment

Product Version: 7.9

Resolution

Here is a steps on how to increase disk:

1. Edit your concourse.yml manifest that is used to deploy concourse.   
2. Depends on which vm the error is thrown assign a vm_type that has larger disk. Highlighted in bold for different components that need disk to be increased

For worker vm

- name: worker
  instances: 1
  azs: ((azs))
  networks: [{name: ((network_name))}]
  stemcell: jammy
  vm_type: ((worker_vm_type))

For web vm

- name: web
  instances: 1
  azs: ((azs))
  networks: [{name: ((network_name))}]
  stemcell: jammy
  vm_type: ((web_vm_type))

For db vm

- name: db
  instances: 1
  azs: ((azs))
  networks: [{name: ((network_name))}]
  stemcell: jammy
  vm_type: ((db_vm_type))

3. do another bosh -d <concourse> deploy concourse.yml for changes to take effect