In a VCF 5.x deployment, SDDC Manager is the source of truth for the components it manages, including the Avi Controller. It stores its own record of the controller's identity and trust material (certificate/thumbprint) and expects that to match what the controller presents.
When a change — most often a certificate replacement — is applied directly in the Avi GUI, SDDC Manager's stored copy no longer matches what the controller now presents. The trust/thumbprint check fails, the account is marked disconnected, and any workflow that depends on that trusted channel (such as an NSX update) fails immediately.
This is configuration drift: two systems that must agree on the controller's certificate no longer do, because the change was made on only one side.
The fix is to remove the out-of-band change and re-apply it through the managed workflow so both sides agree again.