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

Panic error in using user-managed identity #2789

Closed
umagnus opened this issue Aug 26, 2024 · 1 comment · Fixed by #2824
Closed

Panic error in using user-managed identity #2789

umagnus opened this issue Aug 26, 2024 · 1 comment · Fixed by #2824
Assignees
Labels
Milestone

Comments

@umagnus
Copy link

umagnus commented Aug 26, 2024

Which version of the AzCopy was used?

Note: The version is visible when running AzCopy without any argument

azcopy v10.26.0

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

linux

What command did you run?

Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.

azcopy copy --recursive --check-length=false --s2s-preserve-access-tier=false

What problem was encountered?

We use azcopy in csi volume cloning feature and get a panic error in e2e test: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_blob-csi-driver/1551/pull-blob-csi-driver-e2e/1825524122587762688
In this case, we use user-assigned managed identity and get error:

 exit status 2, output: INFO: Scanning...
  INFO: Login with identity succeeded.
  INFO: Authenticating to destination using Azure AD
  INFO: Authenticating to source using Azure AD
  INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

  Job 593e0c6a-37e3-3043-4235-199d5bec421c has started
  Log file is located at: /root/.azcopy/593e0c6a-37e3-3043-4235-199d5bec421c.log

  INFO: Authentication failed, it is either not correct, or expired, or does not have the correct permission PUT https://fuse18ef57d1190249f99f9.blob.core.windows.net/pvc-edbd9da6-10ce-4b03-b37c-9b90d9e8f7e1/data
  --------------------------------------------------------------------------------
  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:6e28f32d-601e-005e-7041-f24c71000000
  Time:2024-08-19T14:10:42.2594362Z</Message></Error>
  --------------------------------------------------------------------------------

  panic: close of nil channel

  goroutine 149 [running]:
  github.com/Azure/azure-storage-azcopy/v10/ste.(*jobMgr).reportJobPartDoneHandler(0xc000519508)
  	/mnt/vss/_work/1/s/ste/mgr-JobMgr.go:718 +0x327
  created by github.com/Azure/azure-storage-azcopy/v10/ste.NewJobMgr in goroutine 1
  	/mnt/vss/_work/1/s/ste/mgr-JobMgr.go:203 +0xc88

However we don't have log file because this is an e2e test, but we found the panic code is here jm.jstm.xferDone:

close(jm.jstm.xferDone)

How can we reproduce the problem in the simplest way?

Can we add a check in the code to fix this panic? Thanks

Have you found a mitigation/solution?

@umagnus
Copy link
Author

umagnus commented Aug 26, 2024

This error only occurred in blob now, and we don't find same issue on file. Is this issue only in blob?

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

Successfully merging a pull request may close this issue.

4 participants
@umagnus @vibhansa-msft @wonwuakpa-msft and others