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

Blob Copy Start doesn't work anymore on 2.25.0 #18539

Closed
benjamin-rousseau-shift opened this issue Jun 18, 2021 · 5 comments · Fixed by #18730
Closed

Blob Copy Start doesn't work anymore on 2.25.0 #18539

benjamin-rousseau-shift opened this issue Jun 18, 2021 · 5 comments · Fixed by #18730

Comments

@benjamin-rousseau-shift

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
It returns 'NoneType is not callable'

To Reproduce
az storage blob copy start --source-blob blob.vhd --source-container vhds --account-name storageaccountname1 --account-key accountkey1 --destination-blob blob.vhd --source-account-name storageaccountname2 --source-account-key accountkey2 --destination-container vhds

Expected behavior
to copy the vhds to the destination

Environment summary
az cli 2.25.0

@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 18, 2021
@yonzhan yonzhan added the Storage az storage label Jun 18, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jun 18, 2021
@yonzhan yonzhan removed the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label Jun 18, 2021
@yonzhan yonzhan added this to the S189 milestone Jun 18, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented Jun 18, 2021

storage

@Juliehzl
Copy link
Contributor

Juliehzl commented Jul 5, 2021

Hi @heavenlyren, could you use az storage blob generate-sas to get a valid sas token and use it as --source-sas for your command?

@Juliehzl
Copy link
Contributor

Juliehzl commented Jul 8, 2021

fixed in PR #18730

@Juliehzl Juliehzl closed this as completed Jul 8, 2021
@benjamin-rousseau-shift
Copy link
Author

Hi @Juliehzl

Has this been fixed in 2.26.0 ?
I did not have the time to test the command you asked. But if I want to upgrade to 2.26.0 do I have to generate sas and use source-sas instead or is that just a workaround ?

@Juliehzl
Copy link
Contributor

Hi @Juliehzl

Has this been fixed in 2.26.0 ?
I did not have the time to test the command you asked. But if I want to upgrade to 2.26.0 do I have to generate sas and use source-sas instead or is that just a workaround ?

The fix will be available in a hotfix version 2.25.1.
After upgrade, you do not need to generate sas by yourself. It is just a workaround.

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

Successfully merging a pull request may close this issue.

3 participants