Unexpected foundation drop in Tanzu Hub after UAA SAML updates
Article ID: 444969
Updated On:
Products
Issue/Introduction
A foundation suddenly becomes invisible in Tanzu Hub, causing all metrics and dashboard visibility for that specific foundation to drop to zero. The connection for the foundation may appear active, but it is not available under the foundation section.
The tas-agent-service on the affected foundation reports an inability to connect to the platform Ops Manager URL due to invalid platform_services_client credentials. The UAA error logs show 404 errors for the client: "http.path":"/uaa/oauth/clients/platform_services_client","http.status_code":"404","error":"404"
Environment
Per Hub documentation (https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-hub/10-4/tnz-hub/foundations-attach-foundation-manual.html), platform_services_client has to be created by the user. As explained in this article, it is expected that Ops Manager UAA will remove user-created users and clients when SAML options are changed. It is also noted in "Creating and managing Tanzu Operations Manager user and client accounts" that "Users created this way do not persist if UAA authentication settings change."
Resolution
To restore visibility, recreate theplatform_services_clienton the platform services and restart thetas-agent-service.
R&D has acknowledged this issue as a product limitation. The UAA team has committed to address this behavior in a future enhancement. Subscribe to this article for updates.
Feedback
