About Uyuni
Uyuni is an open-source systems management platform for Linux estates — the upstream project behind SUSE Manager. It registers Linux servers and workstations, keeps their packages patched, and holds an inventory of what each machine is and how it is configured. Connecting Uyuni to Serval lets workflows read that inventory, so the Linux estate can feed asset records, access reviews, and endpoint-coverage reporting. The Uyuni integration is currently in beta.Uyuni servers are installed inside your own network, so a connection points at your server’s own hostname. Serval must be able to reach that host.
What the Uyuni integration enables
Pre-installed workflows
Get your credentials
- In the Uyuni web UI, sign in as an administrator and go to Users → Create User.
- Create a dedicated account for Serval and give it the roles it needs to read your systems. Read access to the systems you want ingested is enough for the bundled workflow.
- Note the account’s login and password, and your Uyuni server’s hostname.
Connect Uyuni to Serval
- In Serval, go to Settings → Integrations and choose Uyuni.
- Enter your Server URL — the Uyuni server’s hostname, without
https://and without a path (for exampleuyuni.internal.example.com, oruyuni.internal.example.com:8443if it listens on a non-standard port). - Enter the Username and Password of the account you created.
- Optionally set Serial number custom value. Leave it blank unless you have read the note below.
- Save the connection.
Serial numbers and the DMI asset field
Uyuni’s DMI response has anasset field and no dedicated serial-number field, so Serval records asset as the system’s serial number and marks the source as dmi.asset. On some hardware that value is the chassis or board asset tag rather than a manufacturer serial, and on some it is empty.
If your machines carry their real serial in a Uyuni custom value instead, enter that custom-info key in Serial number custom value. Serval will prefer it when it holds a value, and record the source as customValue so you can tell the two apart downstream.
Gotchas and troubleshooting
Your Uyuni server must be reachable from Serval
Your Uyuni server must be reachable from Serval
Uyuni is installed inside your network. If Serval can’t reach the hostname you configured, sign-in fails. Confirm the hostname is correct and that network access from Serval to the server is allowed.
Enter a hostname, not a URL
Enter a hostname, not a URL
The Server URL field takes a hostname (optionally with a port). A value with a path is rejected when you save. Serval adds the
/rhn/manager/api prefix itself.Serval can only see what the account can see
Serval can only see what the account can see
Uyuni scopes systems to organizations, and further by user role. If systems are missing from an ingestion while the connection looks healthy, the configured account cannot see them — check its organization and roles in Uyuni.
Uyuni reports failures with a 200 response
Uyuni reports failures with a 200 response
Uyuni’s HTTP API answers a rejected call with a success flag inside the body rather than an error status. Serval reads that flag and raises the failure, so a permission problem surfaces as a failed step instead of an empty result. If a step fails with a message quoting Uyuni, that message came from your server.
Beta integration
Beta integration
The Uyuni integration is marked beta in the connect screen. Behavior and available capabilities may change.
Need help? Contact support@serval.com for assistance with your Uyuni integration.

