-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ubuntu, Windows] Az Powershell module will be updated to v11.3.1 on March 18 #9445
Comments
Love it |
Deployed |
hey @mikhailkoliada , there is an issue with 11.3.1 which is fixed in 11.4.0. are we able to pin the new version to be pre-installed in the agents instead of 11.3.1 ?? its related to using what-if flag in deployments and causing failures in pipelines using ubuntu and windows agent images, issue is also mentioned here --> Azure/bicep#12112 |
"Actions: Use the AzurePowershell@5 Azure DevOps task to specify a desired version" how to set desired version of Az module? from the link I understand that its the version of Powershell but not of the Az modules |
@chromebohemian448 , used below to install a specific version of Azure PowerShell.
Problem with this approach is that it takes time to install Az modules after a new agent is allocated when running the pipeline using Microsoft hosted agents. It also adds additional time if you have parallel stages since you'll be allocated a new agent/s I believe for a parallel stage/s in your pipeline. Was hoping versions pinned to References: cc: @mikhailkoliada |
So I am experiencing an issue with our build pipeline last seen to work on the 21st March - now fails, no code changes. The 'New-AzSubscriptionDeployment' command was found in the module We are running New-AzSubscriptionDeployment inside a powershell script that runs from AzurePowerShell@5. Have tried Which i think seems to line up with the previous version - and i still get the same error. I tried changing the ubuntu image too (mainly because I got confused as to when the definition of 'latest' had changed) but i get the same message for pinned ubuntu-20.04 What is odd if there is very little 'out there' about this error. if I do as it suggests I get Anyone help? |
If i do that, I am back to the highlighted error. I added the import because the error said to try it... but it sheds no light what-so-ever. I am stumbling around to try and understand what might have changed with the 'ubuntu-latest' which last ran successfully on the 21st March. Looking further at this you can see the image versions etc here: |
If i compare the 'included software' between the two reported urls You can see an announcement "Az Powershell module will be updated to v11.3.1" however across both versions new and old it is/already 11.3.1 and the link it refers to is here... |
So @chromebohemian448's message appears to have disappeared.. you were asking me to remove the 'import' I'd added as the error advised. See my findings. However, I have noticed that in the same time window an awesome package we use 'RegionOrebroLan.Transforming' had changed a version number, and reverting this back - our error disappears. I have no idea at this stage what they could have changed, but the thrust of my investigation goes that way now. |
Breaking changes
Pre-installed Az powershell module on Ubuntu & Windows will be updated to v11.3.1.
Target date
The image rollout process will be started on March 18th and take 3-4 days.
The motivation for the changes
We want to provide a more recent version preinstalled.
Possible impact
If you use direct invocations of Az cmdlets they might be incompatible between major versions of the module so you may need to downgrade your version if it affects your pipeline in workflows unexpected way, we from our side unlikely to help with the code adoption to the new version and most likely all the reports to the runner-images repo will be marked as external and later closed.
Platforms affected
Runner images affected
Mitigation ways
GitHub:
Use the azure/powershell action, it lets you to specify a module version you would like using by passing the
azPSVersion
parameter.Actions:
Use the AzurePowershell@5 Azure DevOps task to specify a desired version
The text was updated successfully, but these errors were encountered: