We have a Bosh concourse setup with 1 db, 2 web instances and 6 workers.
During update of the Concourse Bosh deployment using a pipeline job that is on the same concourse with the default bosh VM update strategy (delete-create), the job fails with error “worker <id….> disappeared while trying to reach it”. However the update continues in the background, that’s why our deploy script is checking if there is such bosh task in the background and joins it, if there is no running task in the background bosh deploy is called as normal.
During update of the Concourse Bosh deployment, using the default ‘delete-create’ bosh update strategy the job fails with error “Volume not found”. However switching top ‘create-swap-delete’ the update process finishes successfully.
Any ideas why this “Volume not found” error is happening and how can we handle it with the default vm update strategy ?