Uyuni container host managed by Uyuni?

[jchristopherlittle]

What issues (if any) might I encounter with my SUSE micro instance that hosts the Uyuni container as a uyuni client/minion to manage the system?

[ppanon2022]

It might explicitly not let you do it? I don't think I've tried - deliberately or by accident - since the containerization, but prior to containerization Uyuni would explicitly not let you register the Uyuni server with itself. It makes some sense in that if a host package upgrade fails and the Uyuni services/container can't start up, then the server is in a catch-22 situation where it can't be fixed until those packages are fixed, but you can't get new packages from the Uyuni server because it isn't up. MicroOS transactional update may make that somewhat more robust but it's not foolproof - I suspect you could still break the host installation (just remove the wrong package, like podman itself) so that the Uyuni container wouldn't start.

[rjmateus]

Hey,
I tested it a few months ago and it was working. However, if you do that you should be aware that the Uyuni host will show up on the systems list, and anyone with access to it will have root access to that host where uyuni is running. If the user has root access to the host OS, it can get root access to all systems registered to uyuni, bypassing all access checks (sure you need to know the right commands and places to touch). This is the main reason we don't think we should advise it.
The other aspect is what you mentioned. If the user messes up the packages then it will break uyuni server. But this can also happen if the user manages the system manually from the console.
Since we are now running on a transitional system, users can rollback to a previous snapshot is something goes wrong, making it much more secure to manage the host OS using uyuni server.