Troubleshooting¶
Intended audience: Anyone who is administering the application.
Known Issues¶
| Issue | Description | Workaround | 
|---|---|---|
| Sasquatch Schema Registry IP changes | During maintenance and upgrades the Sasquatch Schema Registry IP changes. It only causes problems when it restarts since the schema is cached. | 
Monitoring¶
Schema Registry Connectivity Issue¶
Symptoms: There are errors generated for connectivity to the Schema Registry.  Some examples are kafkit.registry.errors.RegistryBadRequestError: Registry error (404). 40403 - Schema 317 not found or httpx.ConnectError.
Cause: The Schema Registry is deployed on Sasquatch in the USDF RSP with a Cluster IP service. During Sasquatch maintenance the IP can change.
- Solution:
- Determine the new Sasquatch IP Address with - kubectl get service sasquatch-schema-registry -n sasquatchon the USDF RSP vCluster. If you do not have access to the vCluster ask on usdf-rsp-support Slack channel.
- Update the - schemaRegistryUrlIP address in the URL of the USDF Prompt Processing Prod Values File.
- Open a PR, merge the changes, then sync in the Next Visit Fan Out App in Argo CD.