Package 'My.Package' was not acquired

Legacy Execution
1

In a script step with a Package Reference, I am seeing an Information message that says:
Package ‘My.Package’ was not acquired

My.Package is a nuget package held in an on-prem nuget repository.

Here’s a snip from the raw log:

09:15:48 Verbose | 7.1.1 extracted to C:\Octopus\Calamari\7.1.1
09:15:48 Verbose | Cleaning up old Calamari versions…
09:15:48 Verbose | Keeping only Calamari version 7.1.1…
09:15:48 Verbose | Found no old versions of Calamari to delete…
09:15:48 Verbose | Process C:\Windows\system32\WindowsPowershell\v1.0\PowerShell.exe in C:\Octopus\Work\20190910161541-142383-5 exited with code 0
09:15:48 Info | Version 7.1.1 of the Calamari tool has been extracted successfully
09:15:49 Verbose | Starting C:\Windows\system32\WindowsPowershell\v1.0\PowerShell.exe in working directory ‘C:\Octopus\Work\20190910161547-142383-6’ using ‘OEM United States’ encoding running as ‘NT AUTHORITY\SYSTEM’ with the same environment variables as the launching process
09:15:49 Verbose | Octopus Deploy: Calamari version 7.1.1
09:15:49 Verbose | Environment Information:
09:15:49 Verbose | OperatingSystem: Microsoft Windows NT 10.0.14393.0
09:15:49 Verbose | OsBitVersion: x64
09:15:49 Verbose | Is64BitProcess: True
09:15:49 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
09:15:49 Verbose | MachineName: APPS
09:15:49 Verbose | ProcessorCount: 2
09:15:49 Verbose | CurrentDirectory: C:\Octopus\Work\20190910161547-142383-6
09:15:49 Verbose | TempDirectory: C:\Windows\TEMP
09:15:49 Verbose | HostProcessName: Calamari
09:15:49 Info | Package ‘My.Package’ was not acquired
09:15:49 Verbose | Performing variable substitution on ‘C:\Octopus\Work\20190910161547-142383-6\Script.ps1’
09:15:49 Verbose | Executing ‘C:\Octopus\Work\20190910161547-142383-6\Script.ps1’

More details on my deployment process:

  • Self-hosted Octopus Server (version 2019.7.12)
  • Tentacles created within same deployment via Terraform hosted in AWS (tentacle version 5.4)
  • Tentacles Registered with Octopus by scripting (this succeeds)
  • Health Check (connection only test) makes tentacles valid deployment targets (this succeeds)
  • Script Step with Package Reference fails on all tentacles with Info message listed above :frowning:
  • Nothing relevant found in logs on Tentacles or Octopus server

Other things to note:

  • Similar script steps with same nuget package work fine targeting an on-prem Octopus Worker
  • Running the failed steps again works immediately with no issue

Any idea what might be going on? I can probably work around this by transferring the package first, but I’d prefer not to have that extra step.

I did notice this issue that was recently fixed:

However, I can’t try that fix as our license just expired and so 2019.7.12 is the last version I can install with our key (getting renewals is a long and laborious process).

3

HI Robert,

Thanks for getting in touch! I’m sorry about the confusion this behavior has caused (and for the misfortune of your license not covering a version with this fix!).

The first thing that I was wondering about was in regards to your health check step. Under the Machine Selection section, do you have Include new deployment targets in the deployment selected (shown in the screenshot below)? If not, does applying this change fix the behavior (note this change will require a new release to be created to apply).

include_new_targets
include_new_targets.png2074×368 30.9 KB

If that doesn’t help matters, would you be willing to supply some additional information to give us more context on your scenario? Specifically a full task log and your deployment process JSON (this can be downloaded in the web portal under the project’s Process tab within the overflow menu).

I look forward to hearing back and getting to the bottom of this one!

Best regards,

Kenny

4

Hi Kenny

Yes, Include new deployment targets in the deployment is selected. In fact, that’s the reason I have the health check. The tentacles are created in AWS in a prior step (via Terraform) and registered with a specific role. I included the health check so I could make the targets available in the same deployment.

I am going to send you a private message with the relevant log and deployment process.

Thanks,

5

@Kenneth_Bates

Hello Kenny

Any updates on this issue?

Thanks,

6

Hi Rob,

Thanks for pinging me about this one. I’m sorry about the delay in getting back to you. I’m letting you know here that I’ve responded to your private message. Let me know how you go or if you have any other questions or concerns going forward.

Best regards,

Kenny

7

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