[jira] [Commented] (BROOKLYN-430) Azure ARM provisioning fails sometimes - no retry when rate limited
[ https://issues.apache.org/jira/browse/BROOKLYN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838071#comment-15838071 ] Aled Sage commented on BROOKLYN-430: Fixed (worked around) in https://github.com/apache/brooklyn-server/pull/535. Marking as resolved, but we should revisit the workaround if/when this is fixed in jclouds. > Azure ARM provisioning fails sometimes - no retry when rate limited > --- > > Key: BROOKLYN-430 > URL: https://issues.apache.org/jira/browse/BROOKLYN-430 > Project: Brooklyn > Issue Type: Bug >Reporter: Aled Sage > Fix For: 0.11.0 > > > Deploying to azure-arm (with Brooklyn 0.11.0-SNAPSHOT, using jclouds 2.0.0) > will often fail due to rate limiting from the azure API. > This is reported in jclouds at > https://issues.apache.org/jira/browse/JCLOUDS-1229 > There is a workaround at https://github.com/apache/brooklyn-server/pull/535 > Once this is fixed in jclouds, and once we've upgraded to an official jclouds > release that includes the fix, then we should delete the workaround added in > PR #535. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (BROOKLYN-430) Azure ARM provisioning fails sometimes - no retry when rate limited
[ https://issues.apache.org/jira/browse/BROOKLYN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837917#comment-15837917 ] ASF GitHub Bot commented on BROOKLYN-430: - Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/535 Thanks @tbouron - LGTM. Once jenkins has finished running the tests, I'll merge this. I've created https://issues.apache.org/jira/browse/BROOKLYN-430 to track this in brooklyn, which just links to jclouds https://issues.apache.org/jira/browse/JCLOUDS-1229. > Azure ARM provisioning fails sometimes - no retry when rate limited > --- > > Key: BROOKLYN-430 > URL: https://issues.apache.org/jira/browse/BROOKLYN-430 > Project: Brooklyn > Issue Type: Bug >Reporter: Aled Sage > > Deploying to azure-arm (with Brooklyn 0.11.0-SNAPSHOT, using jclouds 2.0.0) > will often fail due to rate limiting from the azure API. > This is reported in jclouds at > https://issues.apache.org/jira/browse/JCLOUDS-1229 > There is a workaround at https://github.com/apache/brooklyn-server/pull/535 > Once this is fixed in jclouds, and once we've upgraded to an official jclouds > release that includes the fix, then we should delete the workaround added in > PR #535. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
