-
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
Error setting up Azcopy on newly created VM #12827
Comments
can you share the debug logs, you can create debug logs by adding system.debug variable with value as true |
@monastorm Can you try adding a delay of around 30-40 seconds after the VM creation and before the Az File Copy task and let us know if that helps? |
@eaarora-ms I already tried to add a 60 seconds sleep in my AzurePS script that runs immediately before the Azure File Copy task. This script also runs an Invoke-AzVMRunCommand on the newly created VM, and that command works fine |
Can you please set the variable "System.debug" with value "true". Redeploy and share logs. |
@eaarora-ms @chshrikh, attached please find the debug log. |
@20shivangi To look into it. |
Type: Bug
Task Name: Azure File Copy V4.* (preview)
Environment
Issue Description
When I run Azure File Copy task as the next task after creating an Azure VM, the task fails. When I run the pipeline again (using the same VM), the tasks succeeds.
Error logs
2020-05-05T09:57:23.1013405Z VERBOSE: Preparing to expand...
2020-05-05T09:57:23.1013839Z
2020-05-05T09:57:23.1027686Z VERBOSE: Adding 'C:\ADO_AzCopyV10\AzCopy'.
2020-05-05T09:57:23.1028122Z
2020-05-05T09:57:23.1041746Z VERBOSE: Created 'C:\ADO_AzCopyV10\AzCopy\AzCopy.exe'.
2020-05-05T09:57:23.1042249Z
2020-05-05T09:57:23.1061632Z VERBOSE: AzureFileCopyRemoteJob threw exception
2020-05-05T09:57:23.1061939Z
2020-05-05T09:57:23.1744534Z Invoke-Expression : The term 'azcopy' is not recognized as the name of a
2020-05-05T09:57:23.1745043Z cmdlet, function, script
2020-05-05T09:57:23.1745754Z At line:1 char:1
2020-05-05T09:57:23.1746558Z + & 'C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe' -NoLogo ...
2020-05-05T09:57:23.1747444Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2020-05-05T09:57:23.1748351Z + CategoryInfo : NotSpecified: (Invoke-Expressi...nction, script
2020-05-05T09:57:23.1749080Z :String) [], RemoteException
2020-05-05T09:57:23.1749754Z + FullyQualifiedErrorId : NativeCommandError
2020-05-05T09:57:23.1750284Z
2020-05-05T09:57:23.1750511Z
2020-05-05T09:57:23.1761071Z
2020-05-05T09:57:23.1804416Z file, or operable program. Check the spelling of the name, or if a path was
2020-05-05T09:57:23.1805022Z included, verify that
2020-05-05T09:57:23.1805224Z
2020-05-05T09:57:23.1805365Z
2020-05-05T09:57:23.1817068Z
2020-05-05T09:57:23.1858725Z the path is correct and try again.
The text was updated successfully, but these errors were encountered: