Automatic deployments deploy multiple times to tenants with no available deployment targets

[dan-close]

Team

• [X] I've assigned a team label to this issue

Severity

1 client reporting issue

Version

2022.3.10594

Latest Version

I could reproduce the problem in the latest build

What happened?

Automatic deployments are deployed multiple times to tenants with no available or healthy deployment targets. We would expect these tenants to be skipped altogether using the Skip and continue option for unavailable deployment targets or the Exclude option for unhealthy deployment targets in the project's deployment settings.

The deployments created for the tenants with no targets also cannot be accessed from the Octopus UI. Clicking into the task renders a blank screen and a 404 on the API call to the deployment.

Project Settings:

Deployments: Test Tenant C has no available deployment target and should be skipped.

Reproduction

• Create a Lifecycle that will automatically deploy to an environment.
• Create multiple tenants associated with the test project and the environment set for automatic deployments.
• Associate one of the tenants with a healthy deployment target and another tenant with a disabled deployment target.
• In your project, create a new channel and link it to your new lifecycle.
• Create a new release in the new channel.

Error and Stacktrace

No response

More Information

Internal Support Ticket shortcut

Workaround

No response