Bug - Same release directory used for 2 releases

[benito103e]

Hello,

I deploy a rather classical SF4 application with the usual tasks with Deployer v6.

However, sometimes and randomly, when deploying to several instances in parallel, from some workstations only: the symlink seems to be moved to the new release before the deployment is finalized.
The problem is that the build of the assets (yarn+encore) deletes the manifest.json which crashes the application for a few seconds, until the deployment finishes.

I looked at the code of the different tasks: no clue.
Would the new release work on the current release instead of a new one? But I don't see why...
No weird logs (even in verbose) : everything seems to work fine...

Does anyone have a clue to this problem?

Thanks in advance.

[benito103e]

I just found the source of the problem but not the reason.
The same release directory is used for 2 deployments when it crashes.
For example, today (in the .dep log file):
20220704135139,942
20220704145439,942

[benito103e]

The only thing I see is that the "release" link was not removed at the end of the previous deployment.
And on the new deployment the "deploy:release" does a run('rm -rf "$(readlink release)"');

I can see this log line in a failed deployment:
[*****] > cd /var/www/**** && (rm -rf "$(readlink release)")

The question then becomes, why didn't the previous deployment remove "release" during the cleanup.

[benito103e]

As I mentioned in the linked issue, the problem seems to come from the synchronization (unison) process between our production instances.