One of our ADO release pipeline is currently encountering an error:
Error: Request timeout:/LatestTools
Error: Unable to locate and download the latest Octopus CLI Tool. To use the embedded copy or another specific version, add the Octopus CLI installer task to the build pipeline before this task.
The pipeline was working before this update any idea on what is causing this and do we now have to add the Octopus CLI Installer task to get past this error.
Appreciate the help.
Hi @Quads71 !
Thanks for reaching out, and sorry to hear that you’re having issues with your deployment pipeline. From the looks of this error, your ADO instance is failing to reach out to https://g.octopushq.com/LatestTools (which is a friendly URL pointing to https://download.octopusdeploy.com/octopus-tools/latest.json) to download the latest version of the Octopus CLI that it uses to perform Octopus-related operations. If this is a self-hosted install, is it possible that you have this locked down to disallow access?
One option you may want to use to get unblocked is to change the Octopus CLI tool from latest to embedded here, while you examine the rest of your network configuration to see if anything changed.
I hope this helps!
Thank you Justin for the quick response I will let our team know to check this setting since our Octopus instance is locally managed.
Hi Justin,
Per your comment is the setting in Octopus Deploy or are you referring to ADO itself regarding the access setting?
I was referring to this comment “If this is a self-hosted install, is it possible that you have this locked down to disallow access?”
But regarding the task are you suggesting just to add a task for it? In our current release pipeline we only have a Create and Deploy task prior to this latest upgrade of the extension and that works fine until after the update.
Oh, sorry for the misunderstanding. If you have limited egress to the outside internet from that machine (only allowing whitelisted URLs, or needing a proxy configured etc), it could be an environmental problem outside of ADO/Octopus. You can likely test this by RDP’ing into that machine, and then doing an
Invoke-WebRequest g.octopushq.com/LatestTools and checking to see the output, which should look like:
StatusCode : 200 StatusDescription : OK Content : {"latest":"7.4.3116","downloads":[{"template":"https://download.octopusdeploy.com/octopus-tools/{version}/OctopusTools.{version}.{platform}-{architecture}{extension}","location":"https://download.octo…
RawContent : HTTP/1.1 200 OK
Date: Mon, 22 Feb 2021 20:02:24 GMT
Connection: keep-alive
Set-Cookie: __cfduid=df4a90c5bfc2e6b82fce63c7ffc8bf6b11614024144; expires=Wed, 24-Mar-21 20:02:24 GMT; path=/; domain=.octopu…
Headers : {[Date, System.String[]], [Connection, System.String[]], [Set-Cookie, System.String[]], [ETag, System.String[]]…}
Images : {}
InputFields : {}
Links : {}
RawContentLength : 1827
RelationLink : {}
If it fails to connect, then I imagine it’s an environmental issue that’s preventing the Octopus Plugin to get the latest version of the Octopus CLI.
If the above doesn’t work, I’d have your server/network teams take a look at why this request is failed. If you need to get this deployed now, I’d suggest adding the “Octopus CLI Installer” step to your job, and using the “Embedded” version there, so it won’t try to go out and pull down the latest version (and fail).
thank you for the clarification will check it out.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.