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

Failed to upload playbook to Cloud Shell: StorageError: Forbidden #133

Closed
hadr10 opened this issue Jul 3, 2018 · 9 comments
Closed

Failed to upload playbook to Cloud Shell: StorageError: Forbidden #133

hadr10 opened this issue Jul 3, 2018 · 9 comments
Assignees

Comments

@hadr10
Copy link

hadr10 commented Jul 3, 2018

Environment

  • Extension version:
  • OS Type: Windows

Summary

when I run in vscode: Ansbile: run ansible playbook in cloud shell I get this error message:
Connecting to Cloud Shell.............
Failed to upload playbook to Cloud Shell: StorageError: Forbidden

Reproduce steps

when I run in vscode: Ansbile: run ansible playbook in cloud shell I get this error message:
Connecting to Cloud Shell.............
Failed to upload playbook to Cloud Shell: StorageError: Forbidden

Expected Results

That I connect to cloud shell successfully

Actual Results

Connecting to Cloud Shell.............
Failed to upload playbook to Cloud Shell: StorageError: Forbidden

@yungezz
Copy link
Contributor

yungezz commented Jul 19, 2018

@hadr10 thanks for reporting the issue. could you pls try to upload something to your cloud shell through portal?

@yungezz
Copy link
Contributor

yungezz commented Jul 24, 2018

@hadr10 v0.3.0 released, with a change to create CloudShell with sdk api. could you pls retry it and let us know if still the error?

@hadr10
Copy link
Author

hadr10 commented Jul 26, 2018

I tried with new version and the error is the same

@hadr10
Copy link
Author

hadr10 commented Jul 26, 2018

image

@yungezz
Copy link
Contributor

yungezz commented Jul 27, 2018

Finally I reproduced the error on one of my laptop. Debugging found that ansible extension got correct acocunt key and account name, but call into Azure Storage service got a 403. The issue isn't reproducable with my account on any other machine. I did a search seems it's caused by client machines' time is out sync of services. It's environment related. I've created an issue in azure-storage repo to get help.

Meanwhile, @hadr10 could you pls try it from another machine, without any hyper-v or dual boot system, to see if the error persistent?

@yungezz
Copy link
Contributor

yungezz commented Jul 27, 2018

@yungezz yungezz self-assigned this Jul 31, 2018
@hadr10
Copy link
Author

hadr10 commented Aug 2, 2018

@yungezz thank you

@yungezz
Copy link
Contributor

yungezz commented Sep 11, 2018

workaround by using sas token, after talked with storage sdk team.

@yungezz
Copy link
Contributor

yungezz commented Sep 13, 2018

fixed in release 0.4.0. Pls have a try and let us know if any other issue.

@yungezz yungezz closed this as completed Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants