Foreman and Fedora Silverblue clients


I already searched for answers and hints, but I don’t know if I searched with the wrong keywords.

Is it possible to manage a client with Fedora Silverblue through foreman?
I found some old posts from 2019, that mention I need to enable it with foreman-installer and
the parameter “–ostree” , but this is not mentioned in the documentation for foreman or katello.

What need I to do, to manage a Fedora Silverblue client through foreman?

Hi there,

having not enough knowledge myself about that but out of interest I started poking this use case.

First the docs you are searching for are:

From the first glance it looks like after adding the foreman-installer parameter --foreman-proxy-content-enable-ostree=true you are able to not only add ostree repos to Katello, but also have lifecycles above these repos, aka CVs and LCs work with it.
So yes you can at least clone Fedora’s ostree repo, with one catch, you will need to provide a direct endpoint instead of using the mirrorlist (as configured by default), I got this working by going to and then taking the mirror it gives me.
If I got this right you need to control the normal YUM repos as well, as these are used if you do a rpm-ostree install <package-name> for layered packages, so this can be hooked in the system normally via subscription-manager.
Expect very long cloning times of the ostree repos though, taking a long while for me right now.

The 2nd part, managing clients
Subscription Manager would theoretically have a function to also manage ostree repos, but as far as I know Katello does not provide this functionality. (am testing around with this right now if it still could be used)
But the more known to work way I see right now would be using configuration management for the whole repo management and if needed update applying.
As I expect your clients being workstations they won’t be reachable all the time by the Foreman Server, so this would make it possible to use either Puppet, Salt, or more bare pull-mode job-invocations (with Yggdrasil), that might even get Ansible working on clients if Ansible is installed on the clients (not sure never tried)
And then you just make sure the config files and repo files point in the right direction. (i.e. /etc/ostree/remotes.d/fedora.conf which has the ostree remote in it, or also the rpm-ostreed service config to make it auto update), one downside here is of course, you won’t be able to use authentication for that, every client needs to be able to world read this repo.
The YUM repos will then be controlled normally via rhsm and it’s redhat.repo file.
The point also is, dnf can’t be used, rpm-ostree has to be used, so all job-invocation templates are not ready for that, but you could duplicate and adapt them to this usecase, if you want to be able to package operations via Katello.

To be continued when I got a client in the testsystem.

Also the other thing to think about, ostree-based Fedora encourages the user to use toolbox, containers or Flatpaks for most stuff, controlling that might be another long rabbithole.

You can control container remotes for Podman (and Docker) similarly to how you could do it for the ostree remote, just different files to control via configuration management.
Only getting all used container repos together into Katello might be a bit much work, as you cannot clone the whole or Docker Hub only organizations.

Flatpak though, there is now the option to host individual oci-based Flatpak repos in Katello, but the mass is not that, the fedora remote is though, and especially you can’t again clone the whole Flathub or whole Fedora remote.
As far as I can see the remotes should also similarly as above being able to be controlled, with the /var/lib/flatpak/repo/config file.

For both cases that might take a lot of space, as there is no caching only option for these.

I’m currently at 26h of sync time and still ongoing, looks like the Fedora OSTree enpoint houses all OSTree builds since version 27, that’s gotta be a lot of data. (Looking into getting a include/exclude refs property)

The sync timed out after 2 days, so yeah there is really the need to have the include filter, that might be available in a future version, but not right now.

It gets even better!

After getting the filter function to work, and syncing the fedora/40/x86_64/silverblue ostree head and hooking up a test client.

This has to be done the subscription-manager register method, global host registration is not ready for ostree. Aka.:

rpm-ostree install subscription-manager subscription-manager-plugin-ostree
sudo curl --insecure -o /etc/pki/ca-trust/source/anchors/katello-server-ca.crt
sudo update-ca-trust
sudo curl --insecure -o /root/katello-rhsm-consumer
sudo /bin/bash -x /root/katello-rhsm-consumer 2< /root/katello-rhsm-consumer.log
sudo subscription-manager register --org="my-organisation" --name="" --activationkey="my-activation-key"
sudo vi /etc/dnf/plugins/subscription-manager.conf # change disable_system_repos to 1

This is not necessary, Katello/Subscription Manager also manages the OSTree repo!

Looks like this in the end:

Still leaves the container and flatpak part open, but the rest is manageable out of the box (after getting the Include feature)

1 Like