This message was deleted.
# general
a
This message was deleted.
f
Any hints on debugging that issue?
Bit more context: Both clusters are managed by (different) rancher 2.7.5 installations and are running on v1.25.11+rke2r1 (broken) and v1.25.12+rke2r1 (working). Is it possible that this is a fallout of the AzureAD problem in 2.7.5?