Glad to see things are working again :-) Was that a vhost configuration generated by you? I'd assume yes, as nobody else reported similar issues But if you can't recall, or if you are sure that's not yours, then if you still have the filename, please run rpm -qf <full_path> To see if it's owned by any package we provide (<full_path> being the path where file was) Thanks! El miércoles, 30 de noviembre de 2022 15:17:47 (CET) Crefeld, Tobias LKV Bayern e.V. escribió:

Hi Julio,

the hint with the apache was helpful!

It turned out that there was an old vhost configuration. No idea why it didn't cause troubles in the past and why there is a problem now but after removing the respective vhost config spacewalk-common-channels works as expected now. Afterwards spacewalk-repo-sync populated the channel and mgr-create-bootstrap-repo terminated without missing packages.

-----Ursprüngliche Nachricht----- Von: Julio Gonzalez via Uyuni Users [mailto:users@lists.uyuni-project.org] Gesendet: Dienstag, 29. November 2022 17:31

I'd expect the HTTP 400 from the Uyuni API, and some logs at /var/log/hrn, but maybe somehow the problem is at Apache.

Try to check `/var/log/apache2/` or even the output of `journalctl` (as root).

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com