Channel Default has no available steps

reliability
(Bblankenship) #1

We just upgraded to TeamCity 2019 and the octopus plugin is now failing that worked without issue previously.

Here is the output from TeamCity:

[11:05:43] [Octopus Deploy] Creating Octopus Deploy release
[11:05:43] [Octopus Deploy] Octopus Deploy Command Line Tool, version 6.3.3
[11:05:43] [Octopus Deploy]
[11:05:43] [Octopus Deploy] Detected automation environment: “TeamCity/2019.1.1”
[11:05:44] [Octopus Deploy] Space name unspecified, process will run in the default space context
[11:05:44] [Octopus Deploy] Handshaking with Octopus Server: https://xxx.octopus.app/
[11:05:44] [Octopus Deploy] Handshake successful. Octopus version: 2019.5.12; API version: 3.0.0
[11:05:44] [Octopus Deploy] Authenticated as: T Service Account (a service account)
[11:05:44] [Octopus Deploy] This Octopus Server supports channels
[11:05:44] [Octopus Deploy] Finding project: api-pipeline
[11:05:44] [Octopus Deploy] Building release plan for channel ‘Default’…
[11:05:44] [Octopus Deploy] Finding deployment process…
[11:05:44] [Octopus Deploy] Finding release template…
[11:05:44] [Octopus Deploy] Using version number provided on command-line: 1.2.0.1638-develop
[11:05:44] [Octopus Deploy] Release plan for api-pipeline 1.2.0.1638-develop
[11:05:44] [Octopus Deploy] Channel: ‘Default’ (this is the default channel)
[11:05:44] [Octopus Deploy]
[11:05:44] [Octopus Deploy] Channel Default has no available steps
[11:05:44] [Octopus Deploy] This error is most likely occurring while executing Octo.exe as part of an automated build process. The following doc is recommended to get some tips on how to troubleshoot this: https://g.octopushq.com/OctoexeTroubleshooting
[11:05:44] [Octopus Deploy] Exit code: -1
[11:05:44] [Octopus Deploy] Octo.exe exit code: -1
(Dalmiro Grañas) #3

Hi,

Thanks for reaching out! Could you tell me which version of the TC plugin are you running?

It would be great if you could try running locally the same Octo.exe command that’s being executed during the build. That way we would know if the issue is really related to the TC upgrade or not.

Thanks,
Dalmiro