Description
In what area(s)?
/area runtime
What version of Dapr?
1.14
Expected Behavior
The Dapr sidecar crashes and causes the associated application to restart as well
Actual Behavior
The Dapr sidecar logs a warning but continues to run without being subscribed
Steps to Reproduce the Problem
Theoretically this can happen in a variety of ways where the underlying infrastructure fails to create. The way I encountered the issue was by having 2 applications that publish and subscribe to the same topic. They get deployed together so at roughly the same time they would try and create the same topic.
I use Azure Service Bus so while that is not the root cause of the problem, it is a contributor in that if you get 2 requests close to each other to create the same resource, one of the requests may fail.
failed to subscribe to topics: failed to subscribe to topic {topic name}: could not create topic {topic name}
RESPONSE 409: 409 Conflict\nERROR CODE: 409\n--------------------------------------------------------------------------------\n<Error><Code>409<Detail>SubCode=40900. Conflict.
You're requesting an operation that isn't allowed in the resource's current state. To know more visit https://aka.ms/sbResourceMgrExceptions.
Release Note
RELEASE NOTE: FIX Failure to create pubsub infrastructure will no longer leave the sidecar running.