Further to a previous post I made (Intermittent Azure PowerShell Failures), I finally got round to making the changes and I’m having some issues with the given fix.
It was my understanding that, having installed new versions of Azure tools on the Octopus server, these would only be used on an opt-in basis. I.e. I would have to add the variable OctopusUseBundledAzureModules and set its value to False in order for the new tools to be used. However, it appears that the bundled modules are no longer used by any pipelines, irrespective of whether I set this variable or not.
I have added a step to the pipeline that runs az --version and I see the same output whether I have this variable set to True, False or non-existent. Prior to making any of these changes, running the same command showed a different output.
Is this behaviour expected or have I done something wrong?
In my local testing (on version 2020.4.6) I’m not seeing this behavior. When using bundling and run az --version, i get 2.0.50, but when I use the pre-installed and run az --version, I get 2.13.0.
I spun up a local VM with 2019.8.5, and I am definitely seeing the behavior you’re seeing. Whether or not I have that variable, it is showing me 2.13.0, even though the bundled version should be 2.0.50.
I didn’t find any GitHub issues for this specific bug so I’m guessing it got fixed in the process of something in the area being worked on.
As your version is out of the support window for bug fixes, are you able to upgrade to resolve the issue?