Troubleshooting
This chapter describes common problems that can occur when configuring or operating the SUSE Multi-Linux Manager MCP Server and provides guidance for resolving them.
Start troubleshooting with a read-only tool such as list_systems.
Set UYUNI_MCP_LOG_LEVEL=DEBUG temporarily when the default log level does not provide enough information.
Debug logs can contain sensitive operational data; protect and remove them according to your logging policy.
1. Startup problems
| Message or symptom | Resolution |
|---|---|
|
Set |
|
Use a URL such as |
|
Remove paths such as |
|
Set the value to exactly |
The stdio server disconnects immediately |
Run the configured command in a terminal and inspect stderr. Verify the image tag, environment-file path, |
The HTTP client receives a connection error |
Verify the bind address, published port, external route, and that the client URL ends in |
2. Authentication and authorization
| Message or symptom | Resolution |
|---|---|
HTTP 401 or 403 during SUSE Multi-Linux Manager login |
For basic authentication, verify |
OAuth discovery or token validation fails |
Ensure |
MCP authentication succeeds but SUSE Multi-Linux Manager OIDC login fails |
Ensure the token includes both |
A read tool is available but a write tool is missing |
Set |
The user can call a tool but the operation is denied |
Grant only the required SUSE Multi-Linux Manager permissions to the user. MCP availability does not override SUSE Multi-Linux Manager authorization. |
3. Connectivity and certificates
A network error or timeout indicates that the MCP Server could not complete a request to SUSE Multi-Linux Manager.
-
Resolve
UYUNI_SERVERfrom the MCP Server host or container. -
Verify TCP and TLS connectivity to the configured port.
-
Confirm that proxies and firewalls allow the connection.
-
Verify that the server certificate is valid for the configured hostname and that its CA is trusted.
-
Increase
UYUNI_MCP_TIMEOUTonly after checking server and network health.
Do not use UYUNI_MCP_SSL_VERIFY=false as a permanent certificate fix.
4. Tool-call problems
| Message or symptom | Resolution |
|---|---|
A system name is not found or resolves ambiguously |
Call |
|
The |
|
The MCP client does not support elicitation. Pass |
|
Set the complete private key with literal |
System addition reports that the process started |
The bootstrap request exceeded the request timeout but can still be running on SUSE Multi-Linux Manager. Check the system list and server logs before retrying. |
An operation returns |
The elicitation request was declined, cancelled, or not explicitly approved. Review the arguments and invoke the tool again only if the change is intended. |