-
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
[REGRESSION]: Azure File Copy task states successful completion when copy task cancelled #20911
Comments
I'm seeing the same issue, both the initial 403, then the pipeline thinks it has succeeded. |
Task version 5 correctly fails at least (though I'm unsure why it's getting a 403 doing a PUT to storage account - as far as I can see service principal\service connection has necessary permissions) EDIT: And I can confirm as per original report that Task version 3 correctly authenticates to storage account and correctly copies the files. |
Hi @davidb1101 @simonfanz |
@v-schhabra - I do not have a "manage service principal" link on this service connection. Only "Manage service connection roles" which takes me to the IAM page, but with multiple service principles showing which all seem to be related to devops and as you say it's confusing\hard to tell which is the relevant one. Assigning "Storage Blob Data Contributor" to all of them did fix the 403 so a big thanks for that! :) Though IMO the more pressing issue is that version ~6 of this task doesn't seem to detect when the file copy fails, and happily reports that every is OK, making it hard to detect an issue. |
Hi @simonfanz |
New issue checklist
Task name
Azure file copy
Breaking task version
6.0
Last working task version
3.0
Regression Description
When the task tries to copy the files to the storage account, it fails stating it is unauthorized to perform the request, cancels the upload but then proceeds to label the task as completed successfully.
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)
No response
Operation system
windows-latest
Relevant log output
Full task logs with system.debug enabled
No response
Repro steps
The text was updated successfully, but these errors were encountered: