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? I am wondering if the problem is that the users you are using do not have enough rights to handle this request (but in any case that should NOT return HTTP 400 FMPOV, but maybe HTTP 403. So in any case, if this happens at Uyuni 2022.11, it would qualify for a bug report, so Uyuni returns a code that makes sense, and then maybe as a feature request to be considered. El lunes, 28 de noviembre de 2022 15:14:10 (CET) Crefeld, Tobias LKV Bayern e.V. escribió:

Hi,

the command

spacewalk-common-channels -n sles15-sp3-uyuni-client

returns

SUSE Manager username: lkvadmin

SUSE Manager password:

Traceback (most recent call last):

File "/usr/bin/spacewalk-common-channels", line 269, in <module>

client, key = connect(options.user, options.password, options.server)

File "/usr/bin/spacewalk-common-channels", line 119, in connect

key = xmlrpc_login(client, options.user, password)

File "/usr/lib/python3.6/site-packages/uyuni/common/cli.py", line 74, in xmlrpc_login

sessionkey = client.auth.login(username, password)

File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__

return self.__send(self.__name, args)

File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request

verbose=self.__verbose

File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request

return self.single_request(host, handler, request_body, verbose)

File "/usr/lib64/python3.6/xmlrpc/client.py", line 1187, in single_request

dict(resp.getheaders())

xmlrpc.client.ProtocolError: <ProtocolError for localhost/rpc/api: 400 Bad Request>

lkvbayern is SUSE Manager Administrator and Organization Administrator, being created during initial system setup.

I tried another user-ID with the same credentials - same result.

There is another fault. Don't know if it is related to the problem with spacewalk-common-channels described above:

journalctl -f -u uyuni-check-database.service

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8717]: at /usr/lib/perl5/vendor_perl/5.26.1/Spacewalk/Setup.pm line 29.

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8700]: Your database schema already matches the schema package version [uyuni-reportdb-schema-4.3.5-1.21.uyuni2].

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8700]: Schema upgrade: [uyuni-reportdb-schema-4.3.5-1.21.uyuni2] -> [uyuni-reportdb-schema-4.3.5-1.21.uyuni2]

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8726]: Prototype mismatch: sub Spacewalk::Setup::idn_to_ascii: none vs ($;$$) at /usr/lib/perl5/5.26.1/Exporter.pm line 66.

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8726]: at /usr/lib/perl5/vendor_perl/5.26.1/Spacewalk/Setup.pm line 29.

Nov 28 14:28:01 lkv-srvapp39 spacewalk-startup-helper[8738]: Prototype mismatch: sub Spacewalk::Setup::idn_to_ascii: none vs ($;$$) at /usr/lib/perl5/5.26.1/Exporter.pm li

System is running Uyuni 2022.08 on opensuse-15.4.

Any idea how to get spacewalk-common-channels running? A result of the fault is that "mgr-create-bootstrap-repo" and therefore "Bootstrapping" isn't successful any more.

Regards,

Tobias Crefeld.

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