Worker Health Check triggered from UI is checking targets instead

[BobJWalker]

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.

Prerequisites

• I have verified the problem exists in the latest version
• I have searched open and closed issues to make sure it isn't already reported
• I have written a descriptive issue title
• I have linked the original source of this report
• I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

When I am in the UI on my cloud instance (2018.9.11) I go to trigger a health check for my workers.

But when the health check runs it decided to pull in all my targets instead and ignore all my workers.

What I expected to happen

That triggering a health check from the worker screen would health check the workers not the targets.

Steps to reproduce

1. Go to workers screen (/app#/infrastructure/workers)
2. Run health check by clicking on the ... check health
3. Watch as the health check is ran for all targets not workers

Affected versions

Octopus Server: 2018.9.11

Workarounds

Let the scheduled health checks run. This only happens when manually triggering them in the UI.

[droyad]

This is because the UI queues a task with the ArgumentsRestrictedTo set to "DeploymentTargets". Can reproduce in Demo

[octoreleasebot]

Release Note: Fixed issue where worker health checks run for deployment targets instead

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.