Inconsistent behaviour of ATC with create-swap-delete vm-replacement strategy with Concourse v4.2.1

#1

Hi,

We use Concourse version 4.2.1. When we switch from the default vm-replacement strategy (delete-create) of Concourse to create-swap-delete - https://bosh.io/docs/changing-deployment-vm-strategy/ we get the following issue:

  • After redeploying the Concourse deployment you have to recreate all of the workers at least twice (I still have not figured out the exact number of required recreations on order for ATC to find the new worker nodes - sometimes the command ‘fly workers’ finds only one worker and sometimes id does not find any workers - it is completely inconsistent).

We do not experience the issue when we use the default vm-replacement strategy - delete-create.
Has anyone found a solution regarding the above issue with vm-replacement strategy create-swap-delete? Also can someone comment what is the state of the above finding in the latest version of Concourse - 5.0.1 regarding the vm replacement strategy create-swap-delete?

Note: This issue is linked with issue Need help switching from btrfs to overlay in Concourse bosh deployment where we have found the current issue.

Best Regards,
Stoyko Dimitrov

Need help switching from btrfs to overlay in Concourse bosh deployment