El martes, 29 de noviembre de 2022 17:13:24 (CET) Crefeld, Tobias LKV Bayern e.V. escribió:
Hi Julio,
Thanks for you advise!
I tested with different credentials including wrong ones - same return code. And yes, this is the user I defined during initial setup of Uyuni 2 years ago.
There is no change of the log files in /var/log/rhn/ when I start the command including rhn_web_api.log that usually shows activity whenever I work with the repository management. Other commands like spacewalk-repo-sync or spacewalk-remove-channel work fine. If we talk about http return codes my understanding is, that code 400 is indicating malformed client requests.
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).
I will run the update to 2022.11 within the next few days hoping that this will fix the DB-warnings at least. But actually I fear that this won't fix the issue with spacewalk-common-channels
Since you mention this is nto even working with the initial user, please report an issue at the repository, if you can reproduce with 2022.11. Try to attach as many details as possible, including anything you see at the extra logs I mentioned above. BTW: Something that just came to my mind now: did you sync SLE15SP3 from SCC using the Setup Wizard or mgr-sync already? This is required to add the client tools for SLE15SP3, as they used the channels from SUSE as base.
Regards, Tobias Crefeld.
-----Ursprüngliche Nachricht----- Von: Julio Gonzalez via Uyuni Users [mailto:users@lists.uyuni-project.org] Gesendet: Montag, 28. November 2022 16:05 An: 'users@lists.uyuni-project.org' <users@lists.uyuni-project.org> Cc: Crefeld, Tobias LKV Bayern e.V. <Tobias.Crefeld@lkv.bayern.de>; Julio Gonzalez <jgonzalez@suse.com> Betreff: Re: Prob with spacewalk-common-channels
Since you are on 2022.08, I'd recommend updating to 2022.11 already (be ware of the manual steps required, carefully read the release notes)
For the PostgreSQL log, I seem to remember it was something not harmful, but that was fixed on 2022.10.
For the spacewalk-common-channels, I am not sure, but it could be there were some fixes at the API.
In any case, since you see an error HTTP 400 Bad Request, you should also be able to see something at /var/log/rhn/ that explains why the request was incorrect.
Does this problem happen if you use the first user created when you installed Uyuni?
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com