Troubleshooting
Quick troubleshooting
The AI Assistant lives in the Local cluster in the cattle-ai-agent-system
namespace. Agent Logs can be accessed to understand any issues.
kubectl get po -n cattle-ai-agent-systemTo get logs from the ‘rancher-ai-agent’ pod:
kubectl logs -n cattle-ai-agent-system -l app=rancher-ai-agentTo get logs from the ‘rancher-ai-mcp’ pod:
kubectl logs -n cattle-ai-agent-system -l app=rancher-mcp-serverEnable debug log
You can enable debugs log, using log.level=debug during the helm deployment
of the Agent.
|
If you configured the model via the settings page, please report the settings back in the values file before updating. |
...
log:
level: debug
...helm upgrade -n cattle-ai-agent-system -f values.yaml rancher-ai-agent oci://registry.suse.com/rancher/charts/rancher-ai-agentRancher behind insecure certificate
If your Rancher manager is using a self-signed certificate, please use
insecureSkipTls=true to allow the MCP server to connect to Rancher.
|
If you configured the model via the settings page, please report the settings back in the values file before updating. |
...
insecureSkipTls: true
...helm upgrade -n cattle-ai-agent-system -f values.yaml rancher-ai-agent oci://registry.suse.com/rancher/charts/rancher-ai-agent