Ethereum Proof-of-Work Consortium - Deployment Failed

Category: azure blockchain

Question

funkych on Tue, 03 Apr 2018 00:19:19


What should I do to avoid this error. I have pay-as-you-go subscription

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"BadRequest\\\",\\r\\n \\\"message\\\": \\\"Pricing tier doesn't match the subscription billing model\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"}]}

Replies

Microsoft Azure Blockchain Team on Tue, 03 Apr 2018 00:58:26


Greetings,

We believe that it may be the case that your deployment may have crossed the limit set on pay-as-you-go subscriptions.  The information on these limits may be found here.  You may request an increase in the number of resources by requesting Azure Support here.

Thanks.

Shana Matthews on Tue, 03 Apr 2018 19:57:00


Hi! 

I also ran into this issue trying to deploy Ethereum Proof-of-Work Consortium. The deployment fails while trying to deploy the OMS.

"details": [ { "code": "BadRequest", "message": "{\r\n \"error\": {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"Pricing tier doesn't match the subscription billing model\"\r\n }\r\n}"

I'm using an MSDN subscription account for this resource.

Can you give more details on what you mean by the deployment has "crossed the limit"? What limit specifically is the issue? Number of resources? 

AkshayBh on Wed, 04 Apr 2018 11:13:41


can some one confirm if the propose solution. resolves the issue. 

even I am receiving the same error however not sure which limit should I ask quota team to increase?

dayglogee on Wed, 04 Apr 2018 12:34:49


we're getting the same issue too. It would be nice to be able to figure out which limit we've hit...

Arun Innani on Wed, 04 Apr 2018 14:34:43


we're getting the same issue too. It would be nice to be able to figure out which limit we've hit...

Same issue while creating hybrid runbook worker role

Microsoft Azure Blockchain Team on Mon, 09 Apr 2018 18:44:22


Hi,

We're currently investigating this issue. The OMS pricing model recently change, as explained in this blog post. We are looking into a compatibility fix with this new model, and will update you shortly.

TWHarrington on Tue, 10 Apr 2018 15:22:24


Any update on this issue?  Any timing for resolution?

Microsoft Azure Blockchain Team on Wed, 11 Apr 2018 04:07:37


Hi,

We are in the process of rolling out an update that will disable OMS until we can support the new pricing model in a clear way.  The update should be out by tomorrow and we will inform users via this forum's announcement section and on individual threads.  Thanks for your patience!

TWHarrington on Sun, 15 Apr 2018 17:50:28


FYI...tried to deploy again today.  The template did not have any OMS questions/blanks, but the deployment still failed: "deployOMS" - Conflict

AntoniHPunkt on Sun, 15 Apr 2018 21:08:24


Hi,

We are in the process of rolling out an update that will disable OMS until we can support the new pricing model in a clear way.  The update should be out by tomorrow and we will inform users via this forum's announcement section and on individual threads.  Thanks for your patience!


Microsoft Azure Blockchain Team

Hey, can you please give status about a fix? We were forced to redeploy our configuration and are stuck now, what blocks our dev!

juliansap on Wed, 18 Apr 2018 07:58:18


 I noticed that omsDeploy option is missing in UI, but in template properties file i have found that if i put existing workspaceid and primarykey i'm able to deploy from template without errors. This is workaround and OMS should be created before that.      

"omsDeploy": {
            "value": false
        },
        "omsWorkspaceId": {
            "value": "PUT EXISTING VALUE"
        },
        "omsPrimaryKey": {
            "value": "PUT EXISTING VALUE"
        }

TWHarrington on Wed, 18 Apr 2018 17:35:04


Update....I just went through the deployment again through the wizard and it now successfully deploys.

Microsoft Azure Blockchain Team on Fri, 20 Apr 2018 00:49:21


Hello,

This deployment error has currently been mitigated for all customers.