Error with deployment - eventroutes

[rploeg]

Hello,

I want to deploy the solution to an excising IoT Hub environment. I have there already routes to eventgrid, so the deployment give this error ( I think that is the reason):

{ "status": "Failed", "error": { "code": "400126", "message": "Cannot add or remove default routes, default route names are :RouteToEventGrid. If you contact a support representative please include this correlation identifier: bee7c183-a046-4bd8-82a3-ef044e965d2c, timestamp: 2021-04-30 13:43:09Z, errorcode: IH400126." } }

Any idea how I can solve this?

thanks,

Remco

[egoward]

I started getting this error after I started subscribing to events from the hub in my ARM template. My resources would create OK, but updates would fail.

Copying the .properties.routing block for the hub from the portal (which contains a definition for 'RouteToEventGrid') into my ARM template fixed it and the update no longer tries to delete it. Sadly it breaks when I try to create the resources from scratch unless I take the routing block out again.

Not sure if I'm missing something. It feels like the IOT Hub ARM update logic needs to be clearer on when RouteToEventGrid needs to be present. The tutorial here uses utcNow() for resource IDs so it always creates new ones.

[packnologyusa]

I'm having the same problem, and it breaks my CI/CD pipeline in DevOps because I can't deploy ARM template changes to my existing dev environment resource group. All other Azure resources behave as expected (add if new, update if changed, ignore if no changes), it's only the IoTHub resource that fails because of the existing event subscription. This really needs to be fixed if IoTHub can be included in a CI/CD environment.

[imihalcea]

Same issue for us. Any news for a workaround or fix?