Open MRayermannMSFT opened 4 years ago
(AzCopy team) Let's repro this and see what's happening.
To be clear, this is without RBAC, and only using ACLs?
If so, it would make sense why write is failing. However, this is more down to how we fail from permissions issues.
TODO: Investigate if ACL related failures have a specific service code, or something identifiable, so we can determine whether or not to full error out.
There is no special service code for this case. If we want to support this for ADLS Gen 2, special exemptions could be made that just causes this to fail transfers, but not the entire job. Alternatively, we could ask for a special service code.
@JohnRusk @zezha-msft thoughts?
Which version of the AzCopy was used?
10.3.3
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
What problem was encountered?
The final JSON status from AzCopy had a JobStatus of Cancelled:
How can we reproduce the problem in the simplest way?
Create a ADLS Gen2 container with the following folder structure:
Have a user who is given the following ACL permissions:
Have the user use AzCopy (after logging in) to upload a file to
container/New Folder/
.Have you found a mitigation/solution?
No.