Add backwards support to deploy Service Fabric applications using CloudRegion targets

[johnsimons]

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

Old versions that haven't upgraded to the new cloud targets, fail with an exception when deploying:

The step failed: Activity deploy on MyCloud failed with error 'The machine MyCloud will not be deployed to because it is not an AzureServiceFabricCluster target.'.

What I expected to happen

Backwards support to deploy Service Fabric applications using CloudRegion targets should work

Steps to reproduce

1. Install v2018.4.0
2. Create a step to "Deploy Azure Service Fabric Application"
3. You need to use Cloud region targets for this
4. Make sure you can deploy
5. Upgrade to latest version
6. Run deploy again

Screen capture

Log exerpt

16:41:30   Verbose  |       Executing deploy (type Deploy a Service Fabric App) on Octopus Server
16:42:49   Verbose  |       The machine MyCloud will not be deployed to because it is not an AzureServiceFabricCluster target.
16:42:49   Fatal    |       The action deploy on MyCloud failed

Affected versions

Versions prior to v2018.5

Workarounds

Update targets to use the new Azure Service Fabric Cluster target

Links

https://help.octopus.com/t/service-fabric-specifying-target-cluster-for-deployment/20565/8?u=john_simons

[octoreleasebot]

Release Note: Add backwards support to deploy Service Fabric applications using CloudRegion targets

[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.