Is there a way to set the $ErrorActionPreference on Calamari?

nsaia1 · 4 August 2020 18:27

Hi Jeremy,

I had included all the results for what you asked me to run for all tests

Nick Saia | Sr. DevOps Engineer

TITAN School Solutions | www.titank12.com

SOCIALLY INCLINED? Connect with us on for access to our latest information.

DISCLAIMER: This e-mail contains proprietary information, some of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to it. If you are not the intended recipient, you may not use, disclose, copy, print, or rely on this e-mail.

jeremy.miller · 4 August 2020 19:01

Hi Nsaia,

I’m not seeing results from Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full", which should kick out something like this:

CBS           : 1
Install       : 1
InstallPath   : C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
Release       : 528372
Servicing     : 0
TargetVersion : 4.0.0
Version       : 4.8.04084
PSPath        : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
PSParentPath  : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4
PSChildName   : Full
PSDrive       : HKLM
PSProvider    : Microsoft.PowerShell.Core\Registry

The engineers also needed the output from you running the exe generated by building this project:
Please retrieve and build https://github.com/droyad/PSProcessTerminateDemo/tree/master/Demo
and run the exe on the server and let us know what the output is. (We get you to build it so you can see what is going to be run).

Could you please provide both of those?

Thanks,
Jeremy

nsaia1 · 4 August 2020 19:16

Hmm. I sent this earlier this morning. Sending again:

Get-ItemProperty “HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion”

Output:

SystemRoot : C:\Windows
BuildBranch : rs5_release
BuildGUID : ffffffff-ffff-ffff-ffff-ffffffffffff
BuildLab : 17763.rs5_release.180914-1434
BuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
CompositionEditionID : ServerDatacenter
CurrentBuild : 17763
CurrentBuildNumber : 17763
CurrentMajorVersionNumber : 10
CurrentMinorVersionNumber : 0
CurrentType : Multiprocessor Free
CurrentVersion : 6.3
EditionID : ServerDatacenter
EditionSubManufacturer :
EditionSubstring :
EditionSubVersion :
InstallationType : Server
InstallDate : 1587044293
ProductName : Windows Server 2019 Datacenter
ReleaseId : 1809
SoftwareType : System
UBR : 1339
PathName : C:\Windows
ProductId : 00430-00000-00000-AA682
DigitalProductId : {164, 0, 0, 0…}
DigitalProductId4 : {248, 4, 0, 0…}
InstallTime : 132315178939453329
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
PSChildName : CurrentVersion
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

Get-ItemProperty “HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full”

Output:

CBS : 1
Install : 1
InstallPath : C:\Windows\Microsoft.NET\Framework64\v4.0.30319
Release : 528049
Servicing : 0
TargetVersion : 4.0.0
Version : 4.8.03761
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v4\Full
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4
PSChildName : Full
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

Here is the exe output:

Starting child process
curl: no URL specified!
curl: try ‘curl --help’ for more information

jeremy.miller · 4 August 2020 19:32

Hi Nsaia,

I see it all now, thank you for the information. I will pass it off to the engineers and update you when I get more information.

Thanks,
Jeremy

nsaia1 · 4 August 2020 19:43

Thank you. Please let me know. I can be available today as soon as needed.

nsaia1 · 5 August 2020 13:18

Hi Jeremy!

Do you have a update?

Nick Saia | Sr. DevOps Engineer

TITAN School Solutions | www.titank12.com

SOCIALLY INCLINED? Connect with us on for access to our latest information.

DISCLAIMER: This e-mail contains proprietary information, some of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to it. If you are not the intended recipient, you may not use, disclose, copy, print, or rely on this e-mail.

jeremy.miller · 5 August 2020 13:52

Hi Nsaia,

This ticket/issue has been passed to the Product team. It might be a little bit before we hear anything back so unfortunately, if you need to get this going very quickly, you will have to use the workaround I listed above to get around this until we hear back.

Please let me know if you have any questions or concerns in the meantime.

Thanks,
Jeremy

nsaia1 · 5 August 2020 15:48

Ok. Thank you. We’ll see what we can do with workaround and try and standby for progress from the Product team

jeremy.miller · 5 August 2020 17:25

Hi Nsaia,

I am currently trying to setup a repro of your issue for the product team to work with and I cant get your exact issue. I get errors on gcloud commands, but the runbook always finishes successfully with warning.

Can you post your output of gcloud version please?

Thanks,
Jeremy

nsaia1 · 5 August 2020 17:52

Google Cloud SDK 303.0.0

bq 2.0.58

core 2020.07.24

gsutil 4.52

jeremy.miller · 5 August 2020 19:19

Hi Nsaia,

My output is:

Google Cloud SDK 304.0.0

bq 2.0.58

core 2020.07.31

gsutil 4.52

I know its pretty unlikely seeing as the versions are really close, but would you be able to update and see if the issue goes away? I can only get mine to succeed with warning. I can’t get mine to fully fail due to a gcloud progress/success.

Please let me know what you think.

Thanks,
Jeremy

nsaia1 · 5 August 2020 22:44

I updated still see the same error.

Here is the latest version I have:

Google Cloud SDK 304.0.0

bq 2.0.58

core 2020.07.31

gsutil 4.52

jeremy.miller · 6 August 2020 15:29

Hi Nsaia,

I am still working on getting a repro of your exact error to hand off to our engineers.

Please feel free to reach out in the meantime.

Thanks,
Jeremy

jeremy.miller · 7 August 2020 13:11

Hi Nsaia,

I wanted to update you that this issue has been bumped to a higher priority. It appears to be related to a certain version of PowerShell (5.1.17763) on Windows Server 2019. I will update you as the progress moves forward, but please feel free to reach out in the meantime.

Thanks,
Jeremy

nsaia1 · 7 August 2020 13:29

Thank you Jeremy for your help. We are simultaneously trying some work around as we are overdue on a schedule to deprecate these 2016 servers. We are still running into errors with the work around and look forward to a proper solution.

Keep me posted please.

Thank you very much!

Nick Saia | Sr. DevOps Engineer

TITAN School Solutions | www.titank12.com

SOCIALLY INCLINED? Connect with us on for access to our latest information.

DISCLAIMER: This e-mail contains proprietary information, some of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to it. If you are not the intended recipient, you may not use, disclose, copy, print, or rely on this e-mail.

jeremy.miller · 7 August 2020 13:36

Hi Nick,

You’re very welcome. I will most definitely keep you updated.

Have a great weekend.

Thanks,
Jeremy

nsaia1 · 21 August 2020 14:46

Hi Jeremy,

Do you have anymore updates on this?

jeremy.miller · 21 August 2020 18:10

Hi Nick,

My apologies for the lack of communication on this. This is being triaged internally, but have nothing to share in the way of a solution yet, just the workaround described in the GitHub issue. This actually is an intentional change by Microsoft that seems to be in all newer versions of PowerShell.

I’ve created a GitHub issue for you to subscribe to for updates on the progress on here: https://github.com/OctopusDeploy/Issues/issues/6528

Please let me know if you have any other questions or concerns.

Thanks,
Jeremy

benpearce · 15 September 2020 05:33

Hi Nick,

We have spent some time trying to get a reproduction of this issue in our test environment, using the latest version of Octopus Server but haven’t been able to successfully reproduce the issue.

We downloaded the gcloud cli but have had trouble getting your script you provided earlier working. Are you able to provide some additional information on how we can run your script exactly as you listed it?

Since your first communication on this issue, your hosted instance has been upgraded to a newer version, would you please be able to test this again against your Windows 2019 worker and see if you are still seeing the same problem?

If you have a chance, could you also try executing the problem steps using the Octopus Cloud Windows 2019 workers? To do this you will need to create a new Dynamic Worker Pool and select Windows 2019 as the worker type. Your instance will already have a Dynamic Worker pool but it will currently be configured to use a Windows 2016 worker.

Regards
Ben Pearce

system · 16 October 2020 05:33

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