Skip to content
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

AzCopy v10 "panic: send on closed channel" on 403 Response #2703

Open
tommywilkinson opened this issue Jun 4, 2024 · 1 comment
Open

AzCopy v10 "panic: send on closed channel" on 403 Response #2703

tommywilkinson opened this issue Jun 4, 2024 · 1 comment
Labels

Comments

@tommywilkinson
Copy link

tommywilkinson commented Jun 4, 2024

Which version of the AzCopy was used?

10.25

Which platform are you using? (ex: Windows, Mac, Linux)

Windows

What command did you run?

"copy --log-level=INFO --recursive"
(redacted exact details, since it's not terribly relevant to the repro)

What problem was encountered?

User account had owner permissions on storage account but not Storage Blob Data Contributor. Full error message from running azcopy locally:

INFO: Authentication failed, it is either not correct, or expired, or does not have the correct permission PUT https://<storageaccount>.blob.core.windows.net/1js/pr/3045226/wdjs/wac/we-c/debug/suiteux-shell/js/suiteux.shell.npm_mecontrol.rtl.js
--------------------------------------------------------------------------------
RESPONSE 403: 403 This request is not authorized to perform this operation using this permission.
ERROR CODE: AuthorizationPermissionMismatch
--------------------------------------------------------------------------------
<?xml version="1.0" encoding="utf-8"?><Error><Code>AuthorizationPermissionMismatch</Code><Message>This request is not authorized to perform this operation using this permission.
RequestId:3cd177f3-c01e-0050-18a5-b6a35a000000
Time:2024-06-04T17:34:48.4836791Z</Message></Error>
--------------------------------------------------------------------------------

panic: send on closed channel

goroutine 140 [running]:
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).SendXferDoneMsg(0xc037b4fe08?, {{0xc000ef3b00, 0x7a}, {0xc000ef3b80, 0x80}, 0x0, 0xfffffffa, 0x12385, 0x0})
        D:/a/1/s/ste/jobStatusManager.go:72 +0x4e
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobPartMgr).SendXferDoneMsg(0x180a2c3?, {{0xc000ef3b00, 0x7a}, {0xc000ef3b80, 0x80}, 0x0, 0xfffffffa, 0x12385, 0x0})
        D:/a/1/s/ste/mgr-JobPartMgr.go:694 +0x6e
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobPartTransferMgr).ReportTransferDone(0xc000f08230)
        D:/a/1/s/ste/mgr-JobPartTransferMgr.go:992 +0x16c
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).transferProcessor.func1({0x1d7ba20, 0xc000f08230})
        D:/a/1/s/ste/mgr-JobMgr.go:1089 +0xe2
github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).transferProcessor(0xc00039a388, 0x6acaaa856acaaa85?)
        D:/a/1/s/ste/mgr-JobMgr.go:1105 +0xb2
created by github.com/Azure/azure-storage-azcopy/v10/ste.NewJobMgr in goroutine 1
        D:/a/1/s/ste/mgr-JobMgr.go:200 +0xbf1
panic: send on closed channel

Not a big issue, but seems like a relatively expected case to be causing a panic.

How can we reproduce the problem in the simplest way?

Run azcopy in some manner to get a 403 response.

Have you found a mitigation/solution?

Yes. It's just a noisy failure. It prevents ending statistics from being printed properly, but otherwise is not very impactful.

@seanmcc-msft
Copy link
Member

@tommywilkinson thanks for reporting this, we have added this item to our backlog to be fixed in a future release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants