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

promote-all-regions not working #1

Closed
hosungsmsft opened this issue Feb 17, 2016 · 4 comments
Closed

promote-all-regions not working #1

hosungsmsft opened this issue Feb 17, 2016 · 4 comments

Comments

@hosungsmsft
Copy link

Thanks for the great tool, and sorry if I'm not understanding this usage, but my promote-all-regions usage is failing. Looking at the code, I wonder if line 31 in promote.go needs to be changed to use checkFlag(c, regions) or something like that, instead of just regions?

@ahmetb
Copy link
Contributor

ahmetb commented Feb 17, 2016

@hosungsmsft not really. Promoting to all regions happens by issuing an “Update Extension” operation with <Regions/> element dropped in the PUT request body. That's what that function does.

What error are you getting?

@hosungsmsft
Copy link
Author

I kind of thought that, but there's no help page entry on update-extension, so that's why I couldn't be sure about that.

With promote-all-regions, this is what I got:

hosungs@sati:/gitroot/Compute-Runtime-Tux-lad/publish/xml$ extcli promote-all-regions --manifest diagnostic-2.3.3.xml
INFO[0000] UpdateExtension operation starting...
DEBU[0000] Saving used manifest for debugging: /tmp/extension-manifests304796522/manifest641380801
FATA[0004] Error: Error response from Azure. Code: BadRequest, Message: Expected IsInternal to be false and 1 region specified
hosungs@sati:
/gitroot/Compute-Runtime-Tux-lad/publish/xml$

@ahmetb
Copy link
Contributor

ahmetb commented Aug 22, 2016

@hosungsmsft I lost the context on this but I guess it works fine now as this works just fine in EDP.

@ahmetb ahmetb closed this as completed Aug 22, 2016
@boumenot
Copy link
Member

Agreed. I have not seen this issue. I know that I have this issue, but it was my own error due to not following the appropriate promotion progression (1, 2, all).

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

3 participants