Unable to find octo is causing pipeline step to fail

Hi all,

I have an “Octo-Pack” step that is failing even though octo is installed. How can I resolve this error? This is an azure devops/ tfs pipeline and the agent is installed on a linux VM. Thanks in advance. Output -

Starting: Octo-Pack

Task : Package Application
Description : Package your application into a NuPkg or Zip file.
Version : 3.0.222
Author : Octopus Deploy
Help : Version: 3.0.222. More Information

Attempting to contact https://g.octopushq.com to find latest CLI tools
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62141) Warning: Use Cipheriv for counter mode of aes-256-ctr
Checking local tool cache
Found tool in cache: Octo 7.4.3182 x64
Looking for /home/user2/myagent2/_work/_tool/Octo/7.4.3182/x64/*Octo.dll
##[error]Error: Octo wasn’t found in tools directory
##[error]Failed to execute octo pack command. Octo wasn’t found in tools directory
Finishing: Octo-Pack

Showing that octo is installed -
[root@VM ~]# which octo
/bin/octo

Looking in that directory -
[root@VM ~]# ll /home/user2/myagent2/_work/_tool/Octo/7.4.3182/x64/
total 3776
-rw-r–r--. 1 root root 217600 Apr 20 11:41 Autofac.dll
-rw-r–r--. 1 root root 315904 Apr 20 11:41 Markdig.dll
-rw-r–r--. 1 root root 25600 Apr 20 11:41 Microsoft.Extensions.Caching.Abstractions.dll
-rw-r–r--. 1 root root 29696 Apr 20 11:41 Microsoft.Extensions.Caching.Memory.dll
-rw-r–r--. 1 root root 35328 Apr 20 11:41 Microsoft.Extensions.DependencyInjection.Abstractions.dll
-rw-r–r--. 1 root root 20480 Apr 20 11:41 Microsoft.Extensions.Options.dll
-rw-r–r--. 1 root root 27640 Apr 20 11:41 Microsoft.Extensions.Primitives.dll
-rw-r–r--. 1 root root 656384 Apr 20 11:41 Newtonsoft.Json.dll
-rw-r–r--. 1 root root 37376 Apr 20 11:41 NuGet.Common.dll
-rw-r–r--. 1 root root 84992 Apr 20 11:41 NuGet.Frameworks.dll
-rw-r–r--. 1 root root 18944 Apr 20 11:41 NuGet.Packaging.Core.dll
-rw-r–r--. 1 root root 16384 Apr 20 11:41 NuGet.Packaging.Core.Types.dll
-rw-r–r--. 1 root root 160768 Apr 20 11:41 NuGet.Packaging.dll
-rw-r–r--. 1 root root 31232 Apr 20 11:41 NuGet.Versioning.dll
-rw-r–r--. 1 root root 764 Apr 20 11:41 octo
-rw-r–r--. 1 root root 26 Apr 20 11:41 octo.cmd
-rw-r–r--. 1 root root 26 Apr 20 11:41 Octo.cmd
-rw-r–r--. 1 root root 53106 Apr 20 11:41 octo.deps.json
-rw-r–r--. 1 root root 57736 Apr 20 11:41 Octodiff.dll
-rw-r–r--. 1 root root 11656 Apr 20 11:41 octo.dll
-rw-r–r--. 1 root root 10228 Apr 20 11:41 octo.pdb
-rw-r–r--. 1 root root 532872 Apr 20 11:41 Octopus.Cli.dll
-rw-r–r--. 1 root root 1009032 Apr 20 11:41 Octopus.Client.dll
-rw-r–r--. 1 root root 114240 Apr 20 11:41 Octopus.Cli.pdb
-rw-r–r--. 1 root root 14728 Apr 20 11:41 Octopus.CoreUtilities.dll
-rw-r–r--. 1 root root 56200 Apr 20 11:41 Octopus.Versioning.dll
-rw-r–r--. 1 root root 183 Apr 20 11:41 octo.runtimeconfig.json
-rw-r–r--. 1 root root 87432 Apr 20 11:41 Octostache.dll
-rw-r–r--. 1 root root 102912 Apr 20 11:41 Serilog.dll
-rw-r–r--. 1 root root 9216 Apr 20 11:41 Serilog.Sinks.ColoredConsole.dll
-rw-r–r--. 1 root root 6144 Apr 20 11:41 Serilog.Sinks.Trace.dll
-rw-r–r--. 1 root root 46592 Apr 20 11:41 Sprache.dll
[root@VM ~]#

The previous step is “Use Octopus CLI tool verion latest”

Use Octopus CLI tool version latest

View raw log

Starting: Use Octopus CLI tool version latest

Task : Octopus CLI Installer
Description : Install a specific version of the Octopus CLI
Version : 4.2.472
Author : Octopus Deploy
Help : Version: 4.2.472. More Information

Attempting to contact https://g.octopushq.com to find Octopus CLI tool version latest
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
(node:62119) Warning: Use Cipheriv for counter mode of aes-256-ctr
Using Octopus CLI tool version 7.4.3182
Checking local tool cache
Found tool in cache: octo 7.4.3182 x64
Looking for /home/user2/myagent2/_work/_tool/octo/7.4.3182/x64/*octo.dll,/home/user2/myagent2/_work/_tool/octo/7.4.3182/x64/*Octo.dll
Prepending PATH environment variable with directory: /home/user2/myagent2/_work/_tool/octo/7.4.3182/x64
Finishing: Use Octopus CLI tool version latest

Hi @jharper52,

Thanks for reaching out.

In your Octopus “Package” step, can you please try using version 4 of the task if that is not currently selected?

If that doesn’t work, can you please send a screenshot of the setup of your Package step?

Please let me know.

Best,
Jeremy

I changed it to task version “4.*” but am still seeing the error. Screenshot below-

Thanks for your help thus far. I capitalized these filenames and the step is now working -

[root@vm x64]# cp octo.dll Octo.dll
[root@vm x64]# cp octo.runtimeconfig.json Octo.runtimeconfig.json

Hey John,

Thanks for the information.

The latest version of our plugin should have the logic to find both upper and lowercase of the files, which is why I was confused by the error.

If you have time to test at one point, would you be able to return the casing to its lowercase version and delete the pack step and recreate it and see if the issue persists? I’m worried that you will run into this again when the tool gets upgraded to a newer version.

If you don’t have time, I understand.

Once again, thank you for letting me know you’re in a good state and what got you there.

Best,
Jeremy