-
Notifications
You must be signed in to change notification settings - Fork 219
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
No error reported downloading non-existent blob #1931
Comments
@tasherif-msft please take a look |
Hi @gabe-microsoft I am able to repro this - I will consult with the team regarding this behavior and the next steps as this would be a breaking change. I will keep you posted |
I reproduced something similar in #1975. I think the "to-reproduce" github label should be removed and replaced by "bug". |
@marc-hb I have changed the label to improvement. This was something initially done by design - if the file/dir does not exist assume success and show 0 transfers happened. We are now changing the approach to if single file doesn't exist report failure. There's a draft PR atm. |
Do you mean pattern matching / globbing was performed even with a single file argument? I'm just curious.
URL? |
PR has been merged #1981 |
Which version of the AzCopy was used?
10.16.1
Which platform are you using? (ex: Windows, Mac, Linux)
Linux: Ubuntu 20.04.1 (kernel 5.15.0-1021-azure)
What command did you run?
Download a non-existent blob (login not required, same behavior is using SAS token):
azcopy login azcopy cp https://storageacct.blob.core.windows.net/container/path/to/non/existent/blob .
What problem was encountered?
I would expect AzCopy to report an error and exit with a non-zero code since the requested blob does not exist. However, it returns with a successful (0) exit code with the following output:
The text was updated successfully, but these errors were encountered: