-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Question]: AzureFileCopy started to fail on 21st Aug @ just after 12:30 BST. #18859
Comments
@AndrewBates666 , please post exact task version that gives you that error. I mean like this - 5.xxx.yyy. |
It is the standard Azure File Copy task in Azure release pipelines; the only version info I can see is 5.*. Where can I see the full version? Also is it possible to use an old version of a task. This seems to be a problem that is starting to affect other users. See here: #18809 |
Hi, the task version will be visible in task logs, for example: can you please check and confirm the task version in your recent failure pipelines? Thanks |
5.227.0. |
@AndrewBates666 are you sure that you use Microsoft-hosted agent, not self-hosted agent? |
We are having the exact same problem on all our pipelines, which are running as Microsoft-hosted agents. Highly critical as it is blocking our VM deployments. |
We're using the standard Azure DevOps Microsoft-hosted agents and release pipeline. All tasks using AzureFilecopy are failing with the Sanitizer error. Yes, all of our VMs can't currently be deployed so it is critical for us as well. |
Hello everyone, please check and try to run your pipelines now, and if your using Microsoft hosted agents, task should be able to fetch version 5.226.1 (previous working version) Thanks! |
How do we change the classic pipeline task version from 5.* to 5.226.1 ? The drop down for task version only has 5., 4., 3* etc? |
I reran and it picked up 5.226.1 but error : throw "Failed while downloading azcopy.exe from the URL w . I will upload log file now |
I have had to remove some security information so new upload |
@marcusrichards going by the error message, this doesn't look to be an issue from the task end, it's something to do with your pipeline configuration. @AndrewBates666 and others can you all confirm if the reverted version of 5.226.1 is showing a similar error or working fine for you all? |
i have the same problem, but i am using task# 2, and it is still picking 2.227.3 and not 2.226.1 |
AzureFileCopyV2 hasn't been reverted to 226.1 yet, please try if V4 or V5 version can be used. |
@v-mohithgc |
@v-mohithgc testing this now. Pipeline is running so will update once complete |
I have informed the relevant team, they're on it, meanwhile can you confirm the version of your last success run using v2? |
I can confirm it now works @v-mohithgc using AzureFileCopy 5.226.1. |
2.226.1 |
One thing we have noticed @v-mohithgc since using 5.226.1 are a few warnings. I am not sure if they are caused by us or the AzureFileCopy code. But they are as follows. 2023-08-24T11:35:45.3699679Z ##[warning]Both Az and AzureRM modules were detected on this machine. Az and AzureRM modules cannot be imported in the same session or used in the same script or runbook. If you are running PowerShell in an environment you control you can use the 'Uninstall-AzureRm' cmdlet to remove all AzureRm modules from your machine. If you are running in Azure Automation, take care that none of your runbooks import both Az and AzureRM modules. More information can be found here: https://aka.ms/azps-migration-guide 2023-08-24T11:36:23.1642944Z ##[warning]The names of some imported commands from the module 'Microsoft.Azure.PowerShell.Cmdlets.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. 2023-08-24T11:36:26.4002205Z ##[warning]The names of some imported commands from the module 'Az.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb. |
@AndrewBates666 and @PonYehudak can you also share the link of failing pipeline, so we can investigate it further. |
@LeftTwixWand Andrew and I are on the same team and its working our side. Thanks |
Thank you. I upgraded the remote VM and everything is now running ok. Thanks for your super quick response 👍 |
Hey @Griffa87, @AndrewBates666 and @PonYehudak thank you all for the help. I would like to ask you to share the full pipeline log of your first run, where you faced the issue. If you are concerned about safety, you can send it on my Microsoft email: [email protected] |
I have emailed you @LeftTwixWand |
@LeftTwixWand - Also I have emailed you |
V2 has been reverted to 2.226.1, please rerun and check. Thanks |
Hey @Griffa87 and @PonYehudak thank you so much for sharing these details. |
Try to add addition azure powershell task with inline sript before your azure file copy task Have another problem but found this bug. |
Works now, |
AzureFileCopy has started breaking again today; converting useSanitizerActivate cannot convert System.String :(
From: PonYehudak ***@***.***>
Sent: Sunday, August 27, 2023 7:29 AM
To: microsoft/azure-pipelines-tasks ***@***.***>
Cc: Andrew Bates ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/azure-pipelines-tasks] [Question]: AzureFileCopy started to fail on 21st Aug @ just after 12:30 BST. (Issue #18859)
CAUTION: External email. Please do not click on links or attachments unless you know the content is genuine and safe.
@v-mohithgc<https://github.com/v-mohithgc> when i use v4 or v5 i get other errors, i don't have time to try and solve them now. When will V2 be reverted?
V2 has been reverted to 2.226.1, please rerun and check.
Thanks
Works now,
Thank you.
-
Reply to this email directly, view it on GitHub<#18859 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCC662QVLOMNX4ENKOIT5NDXXLSK7ANCNFSM6AAAAAA33TP5AA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
Emails and their contents may be monitored for the purposes of quality control, fact checking and training.
This email, together with any attachments, is confidential and may be privileged. If you have received it in error, please notify the sender and delete it.
Please click here<https://trl.co.uk/permanent-landing-pages/privacy-notice> to view the TRL Privacy Notice.
TRL Limited, registered in England, No. 3142272, registered office: Crowthorne House, Nine Mile Ride, Wokingham, RG40 3GA, UK. VAT Registration 664 625 321.
|
This issue is now resolved. |
Task name
AzureFilecopy
Task version
5.0
Environment 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)
Windows 2019 Datacenter
Operation system
Windows 2019 Datacenter
Question
The text was updated successfully, but these errors were encountered: