Help wanted with AWX / AKS problem

I hope someone can help me.

I upgraded the node pool for our AKS cluster from 2 Standard_D4s_v3 servers to 2 Standard D4as_v7 servers.
The nodes are almost picking their nose because they have very little to do, but since the upgrade I get the following error a few times now:
Task was marked as running but was not present in the job queue, so it has been marked as failed.
I can’t imagine that the change from D4s to D4as has that much impact on the performance of AWX, and CPU/Memory of the nodes never reach very high levels (highest memory usage of the node I’ve seen was around 60%).

I found Task was marked as running in Tower but was not present in the job queue, so it has been marked as failed · Issue #9594 · ansible/awx · GitHub but that issue is still open.

Anyone has a clue why a D4s_v3 wouldn’t show this behaviour and a D4as_v7 would?

Found the problem. it’s not node related but network related:

[pod/awx-web-5dbf6b86f5-xqpgz/awx-web] psycopg.OperationalError: [Errno -2] Name or service not known

[ERROR] plugin/errors: 2 db-server. AAAA: read udp 172.xx.xx.xx:43062->172.xx.xx.xx:53: i/o timeout

Someone updated the DNS servers on the VNET but forgot to add proper firewall rules and forgot to restart coredns, and months later coredns was restarted and no one could remember the DNS server update…