Open MSylvia opened 1 month ago
@MSylvia - Could you please run the pipeline with debug log enabled and share the logs.
@v-snalawade
To test if the warning Both Az and AzureRM modules were detected on this machine
was the cause, I ran a different pipeline on two modified images and got the same error.
With warning (Both Az and AzureRM on machine):
Without warning (Only Az):
Both runs in this pipeline have debug logs enabled.
@MSylvia - I dont see debug logs enabled, please add variable system.debug to true and run pipeline again.
@v-snalawade Here is a new run with debug logs enabled.
With warning (Both Az and AzureRM on machine):
Without warning (Only Az):
@MSylvia - I went through logs and these are not debug logs. please add variable system.debug to true in pipeline variables and run pipeline again, you will get the detailed logs.
@v-snalawade Here is a new run with debug logs actually enabled this time. I mistakenly thought that enabling diagnostics also set debug to true before.
With warning (Both Az and AzureRM on machine):
Without warning (Only Az):
I'm running into the same issue: Breaking task version 6.240.1 6.239.x
It seems like both 240 and 239 are broken when using Az.Accounts v3.0.0
@DmitriiBobreshev I see you made some changes recently to the Azure File Copy tasks. Do you know what might cause the issues we are seeing?
Thanks for the logs, will check and keep you posted on updates
Thanks, are there any workarounds we can employ in the meantime?
From: v-snalawade @.> Sent: Wednesday, June 5, 2024 7:06 AM To: microsoft/azure-pipelines-tasks @.> Cc: Comment @.> Subject: Re: [microsoft/azure-pipelines-tasks] [REGRESSION]: @. failing to load Az.Accounts v3.0.0 module (Issue #19910)
Thanks for the logs, will check and keep you posted on updates
- Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure-pipelines-tasks/issues/19910#issuecomment-2149666752 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYEROG4772D5KSFKUTZZPT3ZF35JDBFKMF2HI4TJMJ2XIZLTTCBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVEYTKNBYGE2DAMJRURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2SMZZGEYDQOBSGMYKI3TBNVS2S2DBONPWYYLCMVWIFJLWMFWHKZNKGEZDQMBZGQZTGNRSURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2UMJWG43TCMBRHAYDDJDOMFWWLKLIMFZV63DBMJSWZAVFOZQWY5LFVI2TQMJXG4YTONBQGWSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44XQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKBSG43DGMJWG4ZYFJDUPFYGLJLJONZXKZNFOZQWY5LFVIZDGMJWGMYTINJSGSBKI5DZOBS2K3DBMJSWZJLWMFWHKZNJGE2TIOBRGQYDCMMCUR2HS4DFUVWGCYTFNSSXMYLMOVS2SMZZGEYDQOBSGMYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIYTEOBQHE2DGMZWGKBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGE3DONZRGAYTQMBRQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRVHAYTONZRG42DANNHORZGSZ3HMVZKMY3SMVQXIZI. You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hi @MSylvia, @jonathanjyi, Most probably the changes not causing the issue as the changes FF for AzureRM migration were ON for a while for both organizations. I see that both pools are using the same image and suspect that there is some inconsistency between PowerShell where the modules are enabling and pwsh which is used for Get-AzAccessToken CmdLet inside AzCopy.exe. Moreover, the other CmdLets as Connect-AzAccount or Set-AzContext(both provided by Az.Accounts) succeeded, which tells us that the module was loaded correctly for PowerShell session but probably wasn't loaded for pwsh. Is it possible to try another a pool with different image to check will it works for you?
Thanks Dmitrii, this was very helpful. I switched images, and it does seem to work.
From: Dmitrii Bobreshev @.> Sent: Wednesday, June 5, 2024 8:36 AM To: microsoft/azure-pipelines-tasks @.> Cc: Mention @.>; Comment @.> Subject: Re: [microsoft/azure-pipelines-tasks] [REGRESSION]: @.*** failing to load Az.Accounts v3.0.0 module (Issue #19910)
Hi @MSylviahttps://github.com/MSylvia, @jonathanjyihttps://github.com/jonathanjyi, Most probably the changes not causing the issue as the changes FF for AzureRM migration were ON for a while for both organizations. I see that both pools are using the same image and suspect that there is some inconsistency between PowerShell where the modules are enabling and pwsh which is used for Get-AzAccessTokenhttps://github.com/Azure/azure-storage-azcopy/blob/main/common/azure_ps_context_credential.go#L125C10-L125C27 CmdLet inside AzCopy.exe. Moreover, the other CmdLets as Connect-AzAccounthttps://dev.azure.com/mseng/VS%20IDE%20-%20Telemetry/_build/results?buildId=28468351&view=logs&j=a5781d42-2f3f-596b-1540-70f475b4668a&t=62431333-4809-58f9-64bf-05d4a003a852&l=2936 or Set-AzContexthttps://dev.azure.com/mseng/VS%20IDE%20-%20Telemetry/_build/results?buildId=28468351&view=logs&j=a5781d42-2f3f-596b-1540-70f475b4668a&t=62431333-4809-58f9-64bf-05d4a003a852&l=2957(both provided by Az.Accounts) succeeded, which tells us that the module was loaded correctly for PowerShell session but probably wasn't loaded for pwsh. Is it possible to try another a pool with different image to check will it works for you?
- Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure-pipelines-tasks/issues/19910#issuecomment-2149958912 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYEROG73C5ZZMFTY6U45ITDZF4H4ZBFKMF2HI4TJMJ2XIZLTTCBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVEYTKNBYGE2DAMJRURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2SMZZGEYDQOBSGMYKI3TBNVS2S2DBONPWYYLCMVWIFJLWMFWHKZNKGEZDQMBZGQZTGNRSURXGC3LFVFUGC427NRQWEZLMQKSXMYLMOVS2UMJWG43TCMBRHAYDDJDOMFWWLKLIMFZV63DBMJSWZAVFOZQWY5LFVI2TQMJXG4YTONBQGWSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44XQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKBSG43DGMJWG4ZYFJDUPFYGLJLJONZXKZNFOZQWY5LFVIZDGMJWGMYTINJSGSBKI5DZOBS2K3DBMJSWZJLWMFWHKZNJGE2TIOBRGQYDCMMCUR2HS4DFUVWGCYTFNSSXMYLMOVS2SMZZGEYDQOBSGMYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIYTEOBQHE2DGMZWGKBKI5DZOBS2K3DBMJSWZJLWMFWHKZNKGE3DONZRGAYTQMBRQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRVHAYTONZRG42DANNHORZGSZ3HMVZKMY3SMVQXIZI. You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@DmitriiBobreshev While switching pools / images worked for @jonathanjyi there still may be a problem because that pool is loading the older version of Az.Accounts
.
Imported module 'Az.Accounts', version: 2.19.0
If/when that pool updates it could still be a problem.
Hi all any update on this? getting same issue
Since pinning the task version also fails, it seems like it could be related to this issue: https://github.com/microsoft/azure-pipelines-tasks/issues/16505
New issue checklist
Task name
AzureFileCopy
Breaking task version
6.240.1
Last working task version
6.239.x
Regression Description
We have a pipeline that is using
AzureFileCopy@6
with a managed identity. It has been in place for about 2 weeks and has been running without issue. On Tuesday the task started failing with the only visible change in the logs being theAz.Accounts
module updating fromv2.9.1
tov3.0.0
.When it fails, we get this error:
In failed runs the listed
Az.Accounts
module version is alwaysv3.0.0
.Runs that executed earlier which passed have a version of
v2.9.1
.Cross contamination of jobs is not possible because a fresh machine with the exact same configuration is used for each run and that configuration has not changed.
I believe it may have been caused by this change from
AzureRM
toAz
: https://github.com/microsoft/azure-pipelines-tasks/commit/f5b22d9c64118dc809b217a09e4e5d8599939429Example runs:
Pass:
v2.9.1
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9600629&view=logs&j=4736f78b-748e-51a8-c3dc-ea7706a06c3d&t=f124d820-a316-55db-635e-ba56d272505a Fail:v3.0.0
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=9613411&view=logs&j=4736f78b-748e-51a8-c3dc-ea7706a06c3d&t=f124d820-a316-55db-635e-ba56d272505aEnvironment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 11
Relevant log output
Full task logs with system.debug enabled
We don't have full task logs with system.debug enabled.
Repro steps