Deployment failure when switching to different channel

Deployment failure when switching to different channel, where this build was deployed fine for our Main channel but when we do a build for our Release Candidate channel the deployment steps fail.
Any suggest as to what I missed in setting up this other channel. we have different SemVerPrereleaseTag’s
Octopus Log is below:

Task ID: ServerTasks-360679
Task status: Failed
Task queued: Tuesday, October 27, 2020 1:23 PM
Task started: Tuesday, October 27, 2020 1:23 PM
Task duration: 39 seconds
Server version: 3.17.10+Branch.master.Sha.76882cd87713a6460439dbabb9c3d5ab8995e769
Server node: M1WAPPODS01-P

                | == Failed: Deploy _Deploy TotalView_ release 2020.10.27.2-main-rc to Main_UAT ==

13:23:37 Info | Step 3: Windows Service - Set Startup Type Octopus Client is disabled, and will not be executed
13:23:37 Verbose | Step 4: Create the Main Release Candidate - Email does not apply to the current environment, and will not be executed
13:23:37 Verbose | Step 5: Deploy Data Svc does not apply to the current environment, and will not be executed
13:23:37 Verbose | Step 7: Deploy Excel Invoice Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 8: Deploy Security Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 9: Deploy Distribution Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 10: Deploy CRM Integration Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 11: Deploy Auto IMS Integration Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 12: Deploy Data Integration Mgr Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 13: Deploy Alert Triggering Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 14: Deploy Vehicle Status Manager Service does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 15: Deploy Custom Report Gen Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 16: Deploy Fuel Card Inventory Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 17: Deploy LeaseWave Trigger Mon Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 18: Deploy Mass Upload Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 19: Deploy Hangfire does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 20: Deploy Odometer Validation Svc does not apply to the current environment, and will not be executed
13:23:37 Verbose | Step 21: Bring TotalView Sites Online does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 22: Deploy TotalView does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 23: Deploy TotalViewVW does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 24: Deploy TotalView Web Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 25: Deploy VW Web Svc does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 26: Deploy Mobile Web Service does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 27: Deploy TotalView OAuth does not apply to the current channel and will not be executed
13:23:37 Info | Step 28: Git - Pull (HTTPS)_create _branch is disabled, and will not be executed
13:23:37 Verbose | Step 29: Send Failure Email - Main does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 31: Send Failure Email - Release does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 32: Send Failure Email - Enhancement does not apply to the current channel and will not be executed
13:23:37 Verbose | Step 33: Send Success Email - Release does not apply to the current environment, and will not be executed
13:23:37 Verbose | Step 34: Send Success Email - Main does not apply to the current environment, and will not be executed
13:23:37 Verbose | Step 36: Send Success Email - Enhancement does not apply to the current environment, and will not be executed
13:23:37 Verbose | Guided failure is not enabled for this task
13:24:14 Info | A failure has been detected so “Send Failure Email - Main - RC” will be run.
13:24:16 Fatal | The deployment failed because one or more steps failed. Please see the deployment log for details.
|
| == Success: Acquire packages ==
13:23:37 Info | Acquiring packages
13:23:37 Info | Making a list of packages to acquire
13:23:38 Verbose | No packages are required on the Octopus Server
13:23:38 Info | Delta compression is enabled for package transfers from the Octopus Server to deployment targets
13:23:38 Verbose | Upload Merchants.TotalView.Deploy.2020.10.27.2-main-rc to M1WAPPODS01-P
| Upload OctopusTools.4.5.0 to M1WAPPODS01-P
13:23:38 Verbose | Checking package cache for package Merchants.TotalView.Deploy.2020.10.27.2-main-rc
13:23:38 Info | Package Merchants.TotalView.Deploy.2020.10.27.2-main-rc was found in cache. No need to download.
13:23:38 Verbose | Using file: D:\Octopus\Packages\Merchants.TotalView.Deploy\Merchants.TotalView.Deploy.2020.10.27.2-main-rc.nupkg
13:23:38 Verbose | Checking package cache for package OctopusTools.4.5.0
13:23:38 Info | Package OctopusTools.4.5.0 was found in cache. No need to download.
13:23:38 Verbose | Using file: D:\Octopus\Packages\OctopusTools\OctopusTools.4.5.0.zip
13:23:41 Info | All packages have been acquired
13:23:41 Verbose | Acquire Packages completed
|
| Success: M1WAPPODS01-P
|
| Success: Upload package Merchants.TotalView.Deploy.2020.10.27.2-main-rc
13:23:40 Verbose | Octopus Deploy: Calamari version 3.7.112
13:23:40 Verbose | Environment Information:
13:23:40 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:40 Verbose | OsBitVersion: x64
13:23:40 Verbose | Is64BitProcess: True
13:23:40 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:40 Verbose | MachineName: M1WAPPODS01-P
13:23:40 Verbose | ProcessorCount: 2
13:23:40 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182338-360679-1322
13:23:40 Verbose | TempDirectory: C:\Windows\TEMP
13:23:40 Verbose | HostProcessName: Calamari
13:23:40 Verbose | Package Merchants.TotalView.Deploy version 2020.10.27.2-main-rc hash 1a356672cf4f7a0dacc10792b1d16e933191c540 has not been uploaded.
13:23:40 Verbose | Finding earlier packages that have been uploaded to this Tentacle.
13:23:41 Verbose | Found 5 earlier versions of Merchants.TotalView.Deploy on this Tentacle
13:23:41 Verbose | - 2020.9.9.3-prod: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg-ecfe467c-7f39-4f28-b509-90841367b086
13:23:41 Verbose | - 2020.9.30.3-prod: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.9.30.3-prod.nupkg-cc708e83-7777-4b57-866e-8a3bf9722d1c
13:23:41 Verbose | - 2020.9.23.2-prod: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.9.23.2-prod.nupkg-ef380ea3-9dbd-4abb-a6f6-dc461c72ad10
13:23:41 Verbose | - 2020.8.5.4-prod: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.8.5.4-prod.nupkg-1e5d164c-9209-42a1-86d8-463470586536
13:23:41 Verbose | - 2020.8.26.1-prod: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.8.26.1-prod.nupkg-86b958b0-b2ac-428c-8b1d-55e97a2bd304
13:23:41 Info | Found matching version 2020.9.9.3-prod: D:\Octopus\Packages\Merchants.TotalView.Deploy\Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg
13:23:41 Info | Uploading package Merchants.TotalView.Deploy (2.215 KB)…
13:23:41 Verbose | Requesting upload…
13:23:41 Info | Beginning streaming transfer of Merchants.TotalView.Deploy.2020.10.27.2-main-rc.nupkg-9f948af7-ed00-4028-99dc-8c9a667e6419
13:23:41 Info | Stream transfer complete
|
| Success: Building delta for Merchants.TotalView.Deploy.2020.10.27.2-main-rc
13:23:41 Info | Using package D:\Octopus\Packages\Merchants.TotalView.Deploy\Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg with hash cb79312166c165aa95712553e9dba20140828746 for creating delta.
13:23:41 Verbose | Signature file Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg.octosig already exists, using D:\Octopus\OctopusServer\PackageCache\Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg.octosig
13:23:41 Verbose | Building delta file: D:\Octopus\OctopusServer\PackageCache\Merchants.TotalView.Deploy.2020.9.9.3-prod_CB793121_to_2020.10.27.2-main-rc_1A356672.octodelta
13:23:41 Verbose | - Using package: D:\Octopus\Packages\Merchants.TotalView.Deploy\Merchants.TotalView.Deploy.2020.10.27.2-main-rc.nupkg.
13:23:41 Verbose | - Using signature: D:\Octopus\OctopusServer\PackageCache\Merchants.TotalView.Deploy.2020.9.9.3-prod.nupkg.octosig
13:23:41 Info | Original package was 2.215 KB, delta file is 2.265 KB (-2.25% size reduction).
13:23:41 Info | Generated delta file size was within 80% of the full package, going to upload the entire package.
|
| Success: Upload package OctopusTools.4.5.0
13:23:40 Verbose | Octopus Deploy: Calamari version 3.7.112
13:23:40 Verbose | Environment Information:
13:23:40 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:40 Verbose | OsBitVersion: x64
13:23:40 Verbose | Is64BitProcess: True
13:23:40 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:40 Verbose | MachineName: M1WAPPODS01-P
13:23:40 Verbose | ProcessorCount: 2
13:23:40 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182338-360679-1323
13:23:40 Verbose | TempDirectory: C:\Windows\TEMP
13:23:40 Verbose | HostProcessName: Calamari
13:23:40 Verbose | Package OctopusTools 4.5.0 hash 5a9543c4cf3b2a1b25433ba2366fbeba1c173e38 has already been uploaded
13:23:40 Info | Package OctopusTools.4.5.0 (752.387 KB) found in cache. No need to upload this 752.387 KB package. Using D:\Octopus\Files\OctopusTools.4.5.0.zip-6789c2da-4073-48bd-be2e-977c40a54a45
|
| == Success: Step 1: Deploy Placeholder Package ==
13:23:44 Verbose | Deploy Placeholder Package completed
|
| Success: M1WAPPODS01-P
13:23:41 Verbose | Octopus Server version: 3.17.10+Branch.master.Sha.76882cd87713a6460439dbabb9c3d5ab8995e769
13:23:41 Verbose | Environment Information:
| OperatingSystem: Microsoft Windows NT 6.3.9600.0
| OsBitVersion: x64
| Is64BitProcess: True
| CurrentUser: CORP\SVC_ODS
| MachineName: M1WAPPODS01-P
| ProcessorCount: 2
| CurrentDirectory: C:\Windows\system32
| TempDirectory: C:\Users\SVC_ODS\AppData\Local\Temp
| HostProcessName: Octopus.Server
| PID: 1896
13:23:41 Info | Deploying package ‘D:\Octopus\Files\Merchants.TotalView.Deploy.2020.10.27.2-main-rc.nupkg-9f948af7-ed00-4028-99dc-8c9a667e6419’ to machine ‘https://m1wappods01-p:10933/
13:23:42 Verbose | Octopus Deploy: Calamari version 3.7.112
13:23:42 Verbose | Environment Information:
13:23:42 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:42 Verbose | OsBitVersion: x64
13:23:42 Verbose | Is64BitProcess: True
13:23:42 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:42 Verbose | MachineName: M1WAPPODS01-P
13:23:42 Verbose | ProcessorCount: 2
13:23:42 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182341-360679-1324
13:23:42 Verbose | TempDirectory: C:\Windows\TEMP
13:23:42 Verbose | HostProcessName: Calamari
13:23:43 Info | Deploying package: D:\Octopus\Files\Merchants.TotalView.Deploy.2020.10.27.2-main-rc.nupkg-9f948af7-ed00-4028-99dc-8c9a667e6419
13:23:43 Verbose | Extracting package to: D:\Merchants\Apps\Main_UAT\Merchants.TotalView.Deploy\2020.10.27.2-main-rc
13:23:43 Verbose | Extracted 1 files
13:23:44 Verbose | The package has been installed to: D:\Merchants\Apps\Main_UAT\Merchants.TotalView.Deploy\2020.10.27.2-main-rc
13:23:44 Verbose | If you would like the package to be installed to an alternative location, please specify the variable ‘Octopus.Action.Package.CustomInstallationDirectory’
13:23:44 Verbose | Adding journal entry:
13:23:44 Verbose |
13:23:44 Verbose | Updating manifest with output variables
13:23:44 Verbose | Updating manifest with action evaluated variables
13:23:44 Verbose | Planning retention policy
13:23:44 Verbose | Successfully finished Deploy Placeholder Package on M1WAPPODS01-P
|
| == Success: Step 2: Deploy Octo Command Line Tool ==
13:23:46 Verbose | Deploy Octo Command Line Tool completed
|
| Success: M1WAPPODS01-P
13:23:44 Verbose | Octopus Server version: 3.17.10+Branch.master.Sha.76882cd87713a6460439dbabb9c3d5ab8995e769
13:23:44 Verbose | Environment Information:
| OperatingSystem: Microsoft Windows NT 6.3.9600.0
| OsBitVersion: x64
| Is64BitProcess: True
| CurrentUser: CORP\SVC_ODS
| MachineName: M1WAPPODS01-P
| ProcessorCount: 2
| CurrentDirectory: C:\Windows\system32
| TempDirectory: C:\Users\SVC_ODS\AppData\Local\Temp
| HostProcessName: Octopus.Server
| PID: 1896
13:23:44 Info | Deploying package ‘D:\Octopus\Files\OctopusTools.4.5.0.zip-6789c2da-4073-48bd-be2e-977c40a54a45’ to machine ‘https://m1wappods01-p:10933/
13:23:45 Verbose | Octopus Deploy: Calamari version 3.7.112
13:23:45 Verbose | Environment Information:
13:23:45 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:45 Verbose | OsBitVersion: x64
13:23:45 Verbose | Is64BitProcess: True
13:23:45 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:45 Verbose | MachineName: M1WAPPODS01-P
13:23:45 Verbose | ProcessorCount: 2
13:23:45 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182344-360679-1325
13:23:45 Verbose | TempDirectory: C:\Windows\TEMP
13:23:45 Verbose | HostProcessName: Calamari
13:23:45 Info | Deploying package: D:\Octopus\Files\OctopusTools.4.5.0.zip-6789c2da-4073-48bd-be2e-977c40a54a45
13:23:46 Verbose | Extracting package to: D:\Merchants\Apps\Main_UAT\OctopusTools\4.5.0_8
13:23:46 Verbose | Extracted 1 files
13:23:46 Verbose | The package has been installed to: D:\Merchants\Apps\Main_UAT\OctopusTools\4.5.0_8
13:23:46 Verbose | If you would like the package to be installed to an alternative location, please specify the variable ‘Octopus.Action.Package.CustomInstallationDirectory’
13:23:46 Verbose | Adding journal entry:
13:23:46 Verbose |
13:23:46 Verbose | Updating manifest with output variables
13:23:46 Verbose | Updating manifest with action evaluated variables
13:23:46 Verbose | Planning retention policy
13:23:46 Verbose | Successfully finished Deploy Octo Command Line Tool on M1WAPPODS01-P
|
| == Failed: Step 6: Deploy Data Svc - Main RC only ==
13:24:14 Fatal | The step failed: Activity Deploy Data Svc - Main RC only on M1WAPPODS01-P failed with error ‘The remote script failed with exit code -1’.
13:24:14 Verbose | Deploy Data Svc - Main RC only completed
|
| Failed: M1WAPPODS01-P
13:23:47 Verbose | Octopus Server version: 3.17.10+Branch.master.Sha.76882cd87713a6460439dbabb9c3d5ab8995e769
13:23:47 Verbose | Environment Information:
| OperatingSystem: Microsoft Windows NT 6.3.9600.0
| OsBitVersion: x64
| Is64BitProcess: True
| CurrentUser: CORP\SVC_ODS
| MachineName: M1WAPPODS01-P
| ProcessorCount: 2
| CurrentDirectory: C:\Windows\system32
| TempDirectory: C:\Users\SVC_ODS\AppData\Local\Temp
| HostProcessName: Octopus.Server
| PID: 1896
13:23:47 Info | Executing script on ‘M1WAPPODS01-P’
13:23:48 Verbose | Octopus Deploy: Calamari version 3.7.112
13:23:48 Verbose | Environment Information:
13:23:48 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:48 Verbose | OsBitVersion: x64
13:23:48 Verbose | Is64BitProcess: True
13:23:48 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:48 Verbose | MachineName: M1WAPPODS01-P
13:23:48 Verbose | ProcessorCount: 2
13:23:48 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182347-360679-1326
13:23:48 Verbose | TempDirectory: C:\Windows\TEMP
13:23:48 Verbose | HostProcessName: Calamari
13:23:48 Verbose | Executing ‘D:\Octopus\Work\20201027182347-360679-1326\Script.ps1’
13:23:50 Verbose | Name Value
13:23:50 Verbose | ---- -----
13:23:50 Verbose | PSVersion 4.0
13:23:50 Verbose | WSManStackVersion 3.0
13:23:50 Verbose | SerializationVersion 1.1.0.1
13:23:50 Verbose | CLRVersion 4.0.30319.42000
13:23:50 Verbose | BuildVersion 6.3.9600.19170
13:23:50 Verbose | PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
13:23:50 Verbose | PSRemotingProtocolVersion 2.2
13:23:50 Verbose | PowerShell Environment Information:
13:23:50 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
13:23:50 Verbose | OsBitVersion: x64
13:23:50 Verbose | Is64BitProcess: True
13:23:50 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
13:23:50 Verbose | MachineName: M1WAPPODS01-P
13:23:50 Verbose | ProcessorCount: 2
13:23:50 Verbose | CurrentDirectory: D:\Octopus\Work\20201027182347-360679-1326
13:23:50 Verbose | CurrentLocation: D:\Octopus\Work\20201027182347-360679-1326
13:23:50 Verbose | TempDirectory: C:\Windows\TEMP
13:23:50 Verbose | HostProcessName: powershell
13:23:51 Verbose | TotalPhysicalMemory: 8388148 KB
13:23:51 Verbose | AvailablePhysicalMemory: 5424104 KB
13:23:51 Info | Attempting to load .NET DLL D:\Program Files\Octopus Deploy\Tentacle\Octopus.Client.dll…
13:23:51 Info | Loaded .NET DLL D:\Program Files\Octopus Deploy\Tentacle\Octopus.Client.dll.
13:23:51 Info | Looking for project Data Svc in Octopus…
13:23:51 Info | Found project Data Svc in Octopus with ID Projects-31
13:23:51 Info | Looking for existing release for Projects-31, version 2020.10.27.2-main-rc in Octopus…
13:24:09 Info | Did NOT find an existing release for Projects-31, version 2020.10.27.2-main-rc in Octopus.
13:24:09 Info | CALLING OCTO.EXE TO CREATE NEW RELEASE…
13:24:14 Info | Octopus Deploy Command Line Tool, version 4.5.0
13:24:14 Info | Handshaking with Octopus server: http://***********
13:24:14 Info | Handshake successful. Octopus version: 3.17.10; API version: 3.0.0
13:24:14 Info | Authenticated as: Octo Command Line Tool - ****************** <> (a service account)
13:24:14 Info | This Octopus Server supports channels
13:24:14 Info | Finding project: Data Svc
13:24:14 Info | Automatically selecting the best channel for this release…
13:24:14 Info | Building a release plan for Channel ‘Enhancement’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Feature A’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Feature B’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Feature C’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Feature D’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Main’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Main Release Candidate’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Production New’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | Building a release plan for Channel ‘Release’…
13:24:14 Info | Finding deployment process…
13:24:14 Info | Finding release template…
13:24:14 Info | There are 2 viable release plans using the provided arguments so we cannot auto-select one. The viable release plans are:
13:24:14 Info | Channel: ‘Main’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: PASS
13:24:14 Info | Channel: ‘Main Release Candidate’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: PASS
13:24:14 Info | The unviable release plans are:
13:24:14 Info | Channel: ‘Enhancement’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Feature A’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Feature B’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Feature C’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Feature D’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Production New’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Channel: ‘Release’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: FAIL
13:24:14 Info | Exit code: -1
13:24:14 Verbose | Updating manifest with output variables
13:24:14 Verbose | Updating manifest with action evaluated variables
13:24:14 Fatal | The remote script failed with exit code -1
13:24:14 Verbose | at Octopus.Worker.Scripting.ScriptResult.EnsureSuccessful()
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.<>c__DisplayClass29_0.b__0()
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.ExecuteWithTransientErrorDetection(Action action, Machine machine)
| at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.ExecuteActionAndInitLoggingContext(PlannedStep step, Machine machine, PlannedAction action)
13:24:14 Fatal | Deploy Data Svc - Main RC only on M1WAPPODS01-P
|
| Success: Step 30: Send Failure Email - Main - RC
13:24:16 Verbose | Send Failure Email - Main - RC completed
|
| Success: Octopus Server
13:24:14 Verbose | Octopus Server version: 3.17.10+Branch.master.Sha.76882cd87713a6460439dbabb9c3d5ab8995e769
13:24:14 Verbose | Environment Information:
| OperatingSystem: Microsoft Windows NT 6.3.9600.0
| OsBitVersion: x64
| Is64BitProcess: True
| CurrentUser: CORP\SVC_ODS
| MachineName: M1WAPPODS01-P
| ProcessorCount: 2
| CurrentDirectory: C:\Windows\system32
| TempDirectory: C:\Users\SVC_ODS\AppData\Local\Temp
| HostProcessName: Octopus.Server
| PID: 1896
13:24:14 Verbose | Email parameters:
13:24:14 Verbose | Subject: Deployment Failure
13:24:14 Verbose | To: nathanmcclenathan@MerchantsFleet.com,steverosen@merchantsfleet.com,andrewoliver@MerchantsFleet.com,RichardAlbrecht@merchantsfleet.com,AlexanderShumakov@merchantsfleet.com,amormioempaces@merchantsfleet.com,samgomez@MerchantsFleet.com,benmcintyre@MerchantsFleet.com,bretmacke@MerchantsFleet.com,jimwright@MerchantsFleet.com,sachingarg@merchantsfleet.com,nageshrai@MerchantsFleet.com
13:24:14 Verbose | Cc:
13:24:14 Verbose | Bcc:
13:24:14 Verbose | Sending email message…
13:24:15 Info | Email sent!
13:24:15 Verbose | Successfully finished Send Failure Email - Main - RC on the Octopus Server
|
| Canceled: Step 35: Send Success Email - Main - RC
13:24:14 Verbose | Step “Send Success Email - Main - RC” runs only when all previous steps succeeded; skipping
|
| == Success: Apply retention policy on Tentacles ==
13:23:47 Info | Apply retention policies…
13:23:47 Info | Tentacle retention policy set to ‘keep all’
13:23:47 Verbose | Apply Tentacle Retention Policy completed
|

Hi Richard,

Thanks for getting in touch! It looks like a lot of these steps are being excluded from the deployment to your Release Candidate channel, which might be because of channel scoping on each step pointing explicitly to the Main channel. If that’s the case, this scoping will mean the steps won’t be considered on deployments within any other channel that’s outside of that scope.

For any steps that you want run regardless of channel you could remove the channel scoping on those steps, or if you want different steps to be run on different channels you can scope steps to the Release Candidate channel explicitly to ensure it only runs for it.

The step’s channel scoping can be referenced under each step in the process tab like the below screenshot, where you can change them in the step’s Conditions section.

Please let me know how you go or if you have any further questions or concerns moving forward! :slight_smile:

Best regards,

Kenny

That does not help since we are on Octopus 3.17.10
All I can do is not include the channel for deployment of a step


in Step 5 I deploy to the Main channel a build which can include the same servers which are include for a different environment for the “Main Release Candidate” channel using different packages

From the log I see the following:
There are 2 viable release plans using the provided arguments so we cannot auto-select one. The viable release plans are:
13:24:14 Info | Channel: ‘Main’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: PASS
13:24:14 Info | Channel: ‘Main Release Candidate’
13:24:14 Info | # Name Version Source Version rules
13:24:14 Info | — ---------------- ---------------------- ---------------- -----------------------
13:24:14 Info | 1 Deploy Package 2020.10.27.2-main-rc User specified Range: PASS Tag: PASS

Main channel versioning rules are set to use"main"
and “Main Release Candidate” versioning rules are set to use “main-rc”


The Deploy of Data Svc looks like this

Hi Richard,

Thanks for following up! I appreciate the additional details. I think I understand this a bit better, but please correct any mistakes I may be making in some assumptions. :slight_smile:

When the script is run to create a release of Data Svc project, it looks like it can’t auto-resolve which channel to create the release in? I’m assuming you’re using the community Chain Deployment step, where in it you can specify the channel to create the release of the secondary project in. Since the channel names match 1 to 1 between the two projects, you could specify the #{Octopus.Channel.Name} variable in that field to create the release in the same channel that the deployment of the first project is going through.

I hope this helps, and please let me know how you go!

Best regards,

Kenny

Kenny,
Thank you for the Reply from Azure DevOps pipeline we use the Create Release Task with the following settings for the Main Channel:


Then for the Release Candidate pipeline we use the following settings for Create Release Task:

is this what you are talking about?

Thank you again for your reply.
Richard

Hi Richard,

Anytime at all! My apologies for not being more clear there. I’m referring to step 6 in the _Deploy TotalView_ project (which is what Azure DevOps is creating the release for in your screenshots) where in the logs of the deployment of this project it’s calling Octo.exe to attempt to create the release of Data Svc where it can’t resolve the channel automatically. What does your Step 6 (Deploy Data Svc - Main RC only) look like? Is it using the Chain Deployment community step template?

My guess is you’d need to pass in the channel name in this step that’s creating the release of Data Svc, which can be specified in the Chain Deployment’s Channel Name field.

This is all based on the assumption that the core issue is that the Data Svc project, during step 6, is unable to create the release correctly because it’s finding 2 viable release plans and can’t resolve on either one.

I hope that helps! If not, it might be worth grabbing a verbose task log to have a more detailed look into what’s going on. This is done by creating two project variables (OctopusPrintVariables and OctopusPrintEvaluatedVariables, both with a value of `True), then creating and deploying a new release. This will write a lot more information on what’s happening in the deployment to the resulting task log.

Best regards,

Kenny

Thank you Kenny,
We using the “Create and Deploy a Release for a Project” step for the Deploy Data Svc - Main RC We use this for all of our deploy steps this has been working for many years with 7 different channels until we added this new channel. Only difference being that some of the deployments are deployed to the same servers as the “Main” channel

Thank you,
Richard

Someone else wrote the step in PowerShell many years ago before I took over. so they must not have coded it to handle this case.

Hi Richard,

Thanks for the follow up, and that this step is a custom written PS script sounds like a good lead. An alternative to debugging the script could potentially be to use the previously mentioned Chain Deployment step instead which can create and deploy releases in another project during deployment, and maybe that would give you results closer to what you’re after?

Let me know how you get on, and don’t hesitate to reach out with any other questions or concerns!

Best regards,

Kenny

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.