Open onionhammer opened 1 year ago
Would you be able to enable debug logs for Dapr and post the full from when the sidecars start? I would like to see if there are issues connecting to placement.
(Connected via Discord & sent details)
I have the same problem, however it starts working randomly after about 10-20 minutes until I deploy again.
@WolfspiritM this was an infrastructure issue that @ItalyPaleAle helped me to resolve. You should enable debug logs in your dapr & send the debug logs to acasupport at microsoft.com.. reference this issue and the name of your aca environment
@ItalyPaleAle @onionhammer Do you know what the issue was with the infrastructure?
We had an identical issue on our Production Environment today, the version of services we're running and the Dapr runtime haven't been updated for weeks now, so it was very concerning to see this happening randomly.
Deleting and recreating the container app environment fixed the issue but obviously this is not a viable solution on our Production systems!
@faheemgani no, it was an internal issue and they said they resolved it on the backend.
This issue is a: (mark with an x)
Issue description
I have bicep scripts which I use to deploy my application to two environments (a QA and prod), which work fine, but creating a third environment with no code changes (just different azure resources), results in the above error.
I have 2 services in the same ACA environment, an actor 'client' and an actor 'server', the 'server' has an actor statestore and starts successfully, the client also has dapr enabled.
Client daprd output:
Server daprd output:
The same client app on QA works fine, deployed with same bicep scripts, same containers
Expected behavior The daprd sidecar for the client should find the daprd sidecar of the server, and invoke actor methods
Actual behavior Daprd sidecar for client shows error indicating it cannot find the actor type