On Thu, 26 Nov 2020 15:38:21 +0100 Michael Calmer
You miss the uyuni-client-tools channel. Check https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/clients-... for "spacewalk-common-channels" command
When you use salt, you do not need them, but also some other packages which might be useful on a client are not available for you. And it will make the errors go away.
So this channel is something that wasn't needed in the past (= 2020/04)? What do you mean with "using salt"? Till now my understanding was that distribution of software and configuration by Uyuni is always done with salt!?
Other option would be to disable the auto generation of the bootstrap repo. See https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/bootstra...
You write "generation", the document says "regeneration" and the configuration item contains the word "generate". Does disabling "server.susemanager.auto_generate_bootstrap_repo" only mean, that the bootstrap repository stays as it is? Or would it mean as well that in future selecting a new "product" like SLES15-SPx no bootstrap repository will be created and bootstrapping new clients with this product won't work?
Hmm, you made a big jump and I think we made some heavy changes in repo-sync. We made the import of packages now in parallel and this bring much more tasks to your server and speed up the import process a lot. This could be the reason for what you see.
Sounds plausible as the increase happens during the night when repositories get synced. Speeding up initial synchronizations is interesting but IMHO for daily updates this is no advantage. It would be fine if it gave back the memory after some time in order to get used for caching during the day. But ok. - if this memory consumption is comprehensible, increasing the limit in our monitoring will be enough for now. Regards, Tobias.