Registering a new target/worker with the same name, but a new type throws unintuitive error

[Justin-Walsh]

Severity

Sev-3

Version

Earliest incident seen was 2023.2, but likely older

Latest Version

I could reproduce the problem in the latest build

What happened?

When attempting to register a new target/worker with the same name, but different type (Listening to Polling etc), Octopus throws an unhelpful Model Endpoint type does not match incoming type error. We should improve this error to help our users determine the cause of the issue.

Reproduction

• Register a Listening tentacle with "SomeName"
• Attempt to register a Polling tentacle or K8s agent with the name "SomeName"
• 💥

Error and Stacktrace

| FATAL | There was a problem with your request.
 - Model Endpoint type does not match incoming type

More Information

No response

Workaround

Use a different name, or rename/delete the old deployment target.