- Uyuni Users

IMPORTANT: Patch for Uyuni Server 2022.11 and Amazon Linux repository syncing
by Julio Gonzalez 02 Dec '22

02 Dec '22

Hello! A user has reported that after the update to Uyuni 2022.11, running spacewalk- repo-sync would fail with a permissions error, when trying to sync certain amazonlinux core channels. If you are affected, repository syncing will fail, and you will see errors similar to those reported at: https://github.com/uyuni-project/uyuni/issues/6244 This was due to a change in a script used by repo-sync, which checked if pages claiming to be mirrorlists were of the right media type. The check was overzealous and excluded some valid types of pages. A patch for Uyuni 2022.11 is now available, in case you are affected, so you do not need to wait for the next Uyuni release. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2022.10 or earlier, update first to 2022.11 normally (make sure you read the release notes, as special steps required if you are not on 2022.10 already), and then apply the patch as explained above. Thanks to eins for the report and the help debugging the issue. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

OES 2023 repos
by Nick Fletcher 02 Dec '22

02 Dec '22

Hi, I'm fairly new to Uyuni and I am evaluating it as a better solution than Micro Focus SMT. I've entered my Micro Focus credentials and I can see all the OES 2018 products but not OES 2023, which I can see on my Micro Focus SMT server. Will OES 2023 appear eventually or do I need to do anything in particular to add these products? I couldn't see anything about this in the documentation. Thanks, Nick

4 9

AW: Prob with spacewalk-common-channels
by Crefeld, Tobias LKV Bayern e.V. 01 Dec '22

01 Dec '22

Hi Julio, this vhost configuration didn't belong to Uyuni. Starting to evaluate Uyuni, we had the idea to add Netbox on the same system to provide data like ip-adresses, etc. for automated installations. It didn't work and afterwards we forgot this software installation. It was based on a tar file so there is no rpm entry for this application but after removing the respective configuration file from /etc/apache2/vhosts.s/ (+ 2 services + directory in /opt) it shouldn't disturb any more. Regards, Tobias Crefeld. -----Ursprüngliche Nachricht----- Von: Julio Gonzalez via Uyuni Users [mailto:users@lists.uyuni-project.org] Gesendet: Mittwoch, 30. November 2022 17:54 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!

1 0

AW: AW: Prob with spacewalk-common-channels
by Crefeld, Tobias LKV Bayern e.V. 30 Nov '22

30 Nov '22

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).

2 1

AW: Prob with spacewalk-common-channels
by Crefeld, Tobias LKV Bayern e.V. 29 Nov '22

29 Nov '22

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 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 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(a)lists.uyuni-project.org' <users(a)lists.uyuni-project.org> Cc: Crefeld, Tobias LKV Bayern e.V. <Tobias.Crefeld(a)lkv.bayern.de>; Julio Gonzalez <jgonzalez(a)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?

3 2

Prob with spacewalk-common-channels
by Crefeld, Tobias LKV Bayern e.V. 28 Nov '22

28 Nov '22

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.

2 1

IMPORTANT: Patch for Uyuni Server 2022.11
by Julio Gonzalez 25 Nov '22

25 Nov '22

Hello! Several users at Gitter and GitHub have reported that after the update to Uyuni 2022.11, they see a notification whith an error message after a reposync for any channel is complete. The error will contain a python stacktrace as described at https://github.com/uyuni-project/uyuni/issues/6193 Uyuni 2022.11, includes a refactor for the System list page to use a dedicated cache table to improve performance. Because of this refactor, each time a repository is synchronized, we need to refresh the information for the minions using such repository. The query that processes such refresh had a bug, and was referring a non- existing reference. A patch for Uyuni 2022.11 is now available, in case you are affected, so you do not need to wait for the next Uyuni release. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2022.10 or earlier, update first to 2022.11 normally (make sure you read the release notes, as special steps required if you are not on 2022.10 already), and then apply the patch as explained above. Thanks to all users that reported the issues, and helped with the debugging. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

spacewalk-repo-sync failed after update 2022.10 to 2022.11
by Thomas Weis 24 Nov '22

24 Nov '22

hello everyone After updating from 2022.10 to 2022.11, after running spacewalk-repo-sync -p opensuse_leap15_4-x86_64, the process aborted with an error. The following error message was generated: 12:26:52 Repo URL: http://download.opensuse.org/distribution/leap/15.4/repo/oss/ 12:26:52 Packages in repo: 96026 12:34:39 No new packages to sync. 12:34:40 12:34:40 Patches in repo: 0. 12:34:45 12:34:45 Importing media products file products. 12:34:45 *** NOTE: Importing mediaproducts file for the channel 'opensuse_leap15_4-x86_64'. Previous media products will be discarded. 12:42:56 Updating overview of 1 systems Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 299, in _execute_wrapper retval = function(*p, **kw) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", line 182, in _execute return self._execute_(args, kwargs) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 322, in _execute_ self._real_cursor.execute(self.sql, params) psycopg2.errors.UndefinedTable: missing FROM-clause entry for table "c" LINE 4: coalesce(c.org_id, 1), ^ During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/spacewalk-repo-sync", line 286, in <module> sys.exit(abs(main() or 0)) File "/usr/bin/spacewalk-repo-sync", line 269, in main elapsed_time, channel_ret_code = sync.sync() File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 705, in sync self.update_servers() File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 739, in update_servers taskomatic.add_to_system_overview_update_queue(row["id"]) File "/usr/lib/python3.6/site-packages/spacewalk/server/taskomatic.py", line 103, in add_to_system_overview_update_queue h.execute(sid=sid) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", line 150, in execute return self._execute_wrapper(self._execute, *p, **kw) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 309, in _execute_wrapper raise sql_base.SQLStatementPrepareError(str(self.dbh), e.pgerror, self.sql) spacewalk.server.rhnSQL.sql_base.SQLStatementPrepareError: ('ERROR: missing FROM-clause entry for table "c"\nLINE 4: coalesce(c.org_id, 1),\n ^\n', "<connection object at 0x7f1c42cd6a08 ; dsn: 'user=uyunidbuser password=xxx dbname=uyuni', closed: 0>", "\n INSERT INTO rhnTaskQueue (org_id, task_name, task_data, priority, earliest)\n VALUES (\n coalesce(c.org_id, 1),\n 'update_system_overview',\n %(sid)s,\n 0,\n current_timestamp\n )\n ") After that it was completely canceled. The update from 2022.10 to 2022.11 ran without errors, the webgui is accessible. what can be done Restore from snapshot? Thanks for support! Regards Thomas

3 3

file.directory and user.present: how to configure dependencies
by Heiner Wulfhorst 24 Nov '22

24 Nov '22

Hi List, I am having trouble configuring dependencies between the existence of a user and his homedir ( a mounted lv ). If I put the user as a requirement for the chown (file.directory) I get a python error: "RecursionError: maximum recursion depth exceeded while calling a Python object". How should I do it? Here's my current code: sapinst: group.present: - gid: 200 sapsys: group.present: - gid: 201 daaadm: user.present: - require: - group: sapsys - group: sapinst - mount: /usr/sap/DAA - uid: 1112 - gid: 201 - home: /usr/sap/DAA - groups: - sapinst chown_/usr/sap/DAA_to_daaadm: file.directory: - name: /usr/sap/DAA - user: daaadm - group: sapsys - require: - user: daaadm Thanks a lot, Heiner

1 0

Uyuni 2022.11 is released!
by Julio Gonzalez 23 Nov '22

23 Nov '22

VERY IMPORTANT: 2022.11 will require a special procedure if you are not upgrading from 2022.10 Make sure you read the release notes for all the versions between the one you are using now, and 2022.11! We are happy to announce the availability of Uyuni 2022.11. Most openSUSE mirrors should already have 2022.11, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.11, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Instructions to disable custom channel automatic synchronization - Allow more tools for network management for the Uyuni Server - Monitoring: Grafana update to 8.5.13 - Monitoring: Fix TLS configuration and enable client certificate authentication for Blackbox exporter - Traditional stack being removed Remember that Uyuni follows a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2022.11 As always, we hope you will enjoy Uyuni 2022.11 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute. Happy hacking! [1] https://www.uyuni-project.org/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

3 5

2022

2021

2020

2019

2018

Uyuni Users