We have a tenanted elastic environment set up with auto triggers for when ‘machine becomes available for deployment’ and we’re noticing issues when we boot multiple new servers up, some servers often do not get deployed to at all. On inspecting the auto-deploy logs, i can see this
The machine abc is not eligible for the auto-deployment of release Releases-31651 (Projects-309, Environments-43, Tenants-1) because a deployment is currently in progress. abc will receive the deployment when it completes.
This machine however never gets deployed to.
If i look at deployments to that specific server, i can see that nothing was in progress when it reported above. The issue always seems to be with the last server to get booted, which makes me think there is a bug when a server becomes available mid ‘processing automatic deployments for triggers’.
We recently upgraded from 2018.6.1 where we never saw this issue.