October 2022 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

Uyuni webui stops responding.
by Simon Avery 27 Oct '22

27 Oct '22

Hi Has anyone encountered an issue with Uyuni where the web interface becomes unresponsive? I've never had this happen before in at least a couple of years usage, but over the past couple of weeks we've had it happen several times to different users and when it happens, it affects all users. The user's web browsers report that no data is sent on page link or reload. Manually running "spacewalk-service restart" brings it back into life within a couple of minutes. This isn't related to the 2022.10 update, since I've held back applying that so far and we're still on 2022.08. The only thing that's changed is a couple of new users, and perhaps something is taking exception to them. (But we're all on similar chrome + windows clients) I've not yet done any serious debugging (each time the priority has been to get it back up), but would appreciate any tips from anyone that's encountered this. (I'll try and remember to run "spacewalk-service status" next time to at least identify which service is faulting) Thanks Simon

3 4

clients can't connect to uyuni server, JWT token
by Haupt, Torsten 25 Oct '22

25 Oct '22

Hi, since some time my clients can't contact the uyuni server. A "zypper ref" shows for example: zypper ref Permission to access 'https://xxxuyuni.xxx.de:443/rhn/manager/download/sle12_5-utilities-x86_64/r…' denied. Abort, retry, ignore? [a/r/i/...? shows all options] (a): i Last contact time in uyuni is also a long time ago. If I copy the url above in a browser, it get: Token is not valid to access repomd.xml in sle12_5-utilities-x86_64: JWT (claims->{"exp":1652861921,"iat":1621325921,"nbf":1621325801,"jti":"kufB_AaMdzSgIr92uq9cfA","org":1,"onlyChannels":["sle12_5-utilities-x86_64"]}) rejected due to invalid claims. Additional details: [The JWT is no longer valid - the evaluation time NumericDate{1666073380 -> 18.10.2022, 08:09:40 MESZ} is on or after the Expiration Time (exp=NumericDate{1652861921 -> 18.05.2022, 10:18:41 MESZ}) claim value.] It seems a token is to old; but how to renew it? Greets Torsten

4 5

Canceled: Uyuni Community Hours
by Julio Gonzalez 24 Oct '22

24 Oct '22

Dear Community: This Friday most of the SUSE Manager team will not be available, including the moderators, so we need to cancel this session. We'll see you in the November session, and meanwhile remember the Community is available at the mailing lists, Gitter and GitHub. Sorry about the inconvenience!

1 0

IMPORTANT: Patch for Uyuni Server 2022.10
by Julio Gonzalez 24 Oct '22

24 Oct '22

Hello! Several users at Gitter have reported that after the Update to Uyuni 2022.10, and after applying the patch from last week, that the cobbler package fails to update, or that the cobbler service is not starting at the Uyuni Server. In such situations some features can be broken, such as: - Onboarding new clients - Removing existing clients - XML-RPC via HTTP - spacecmd - spacewalk-common-channels The problem was causes because of bugs at migration scripts for cobbler itself. Such bugs are only happening for long time Uyuni users where the cobbler configuration is old enough, so most users should not notice this problem. If you are affected, you will see the following error while installing the cobbler package: > schema.SchemaError: Key 'proxy_url_ext' error: > None should be instance of 'str' Or the following error at the logs, when starting cobbler: > cobblerd[32057]: schema.SchemaError: Key 'allow_duplicate_hostnames' error: > cobblerd[32057]: 0 should be instance of 'bool' The fix is at the SR: https://build.opensuse.org/package/rdiff/systemsmanagement:Uyuni:Master/cob… (an OBS account is required to see the diff) A patch for Uyuni 2022.10 to fix both problems was just published, in case you are affected, and so you do not need to wait for Uyuni 2022.11 (this version will also include this fix) You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html Thank to all users that reported the issue, and helped with the debugging Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Disconnected Setup with SMT results in "java.io.FileNotFoundException: /path/to/product_tree.json"
by Srinidhi B 20 Oct '22

20 Oct '22

Hello List, I'm trying to use the contents of my existing SMT12 setup in Uyuni and I've followed the steps documented at: https://www.uyuni-project.org/uyuni-docs/en/uyuni/administration/disconnect… But I'm getting the following error when I run "mgr-sync refresh": uyuni:~ # mgr-sync refresh Refreshing Channel families Please enter the credentials of SUSE Manager Administrator. Login: admin Password: [DONE] Refreshing SUSE products [FAIL] Error: <Fault -1: 'redstone.xmlrpc.XmlRpcFault: unhandled internal exception: com.suse.scc.client.SCCClientException: java.io.FileNotFoundException: /media/SMT/repo/disconnected-setup/product_tree.json (No such file or directory)'> Detailed steps: =============== We use a NFS mount for our SMT servers. On the same NFS mount, I created a new sub-directory called "disconnected-setup" and ran the following two commands: # smt-sync --createdbreplacementfile /tmp/dbrepl.xml # smt-mirror --dbreplfile /tmp/dbrepl.xml --directory /srv/www/htdocs/repo/disconnected-setup/ --fromlocalsmt -L /var/log/smt/smt-mirror-export.log # ls -l /srv/www/htdocs/repo/disconnected-setup/ total 11848 -rw-r--r-- 1 smt www 2 Oct 3 00:07 organizations_orders.json -rw-r--r-- 1 smt www 10006809 Oct 3 00:07 organizations_products_unscoped.json -rw-r--r-- 1 smt www 1744853 Oct 3 00:07 organizations_repositories.json -rw-r--r-- 1 smt www 341708 Oct 3 00:07 organizations_subscriptions.json drwxr-xr-x 4 smt www 4096 Oct 3 04:28 repo lrwxrwxrwx 1 smt www 9 Oct 3 04:28 SUSE -> repo/SUSE Back on the Uyuni server, I ran: # mount -t nfs storage:/srv/ftp/SMT /media/SMT # echo 'server.susemanager.fromdir = /media/SMT/repo/disconnected-setup/' >> /etc/rhn/rhn.conf # systemctl restart tomcat Could someone please tell me what am I missing? How do I get the "product_tree.json" file generated from the SMT server? Regards, Srinidhi.

2 2

IMPORTANT: Patch for Uyuni Server 2022.10
by Julio Gonzalez 20 Oct '22

20 Oct '22

Hello! Several users at GitHub, mailing lists and Gitter have reported that after the Update to Uyuni 2022.10, cobbler is not starting at the Uyuni Server, therefore affecting some features, such as: - Onboarding new clients - Removing existing clients - XML-RPC via HTTP - spacecmd - spacewalk-common-channels The following bug reports are related to this problem: - https://github.com/uyuni-project/uyuni/issues/6037 - https://github.com/uyuni-project/uyuni/issues/6041 - https://github.com/uyuni-project/uyuni/issues/6045 The problem was caused for a bug at the script for the migration of the settings and collections to Cobbler 3.3.3 The fix is at the PR https://github.com/uyuni-project/uyuni/pull/6050 A patch for Uyuni 2022.10 to fix both problems was just published, in case you are affected, and so you do not need to wait for Uyuni 2022.11 (this version will also include this fix) You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html Thank to all users that reported the issue, and helped with the debugging Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

no more OES2018 repos in Uyuni after new key for SLES subscriptions
by Thomas Weis 15 Oct '22

15 Oct '22

Hello everyone we synchronize the current OES2018-SP3 repositories via Uyuni. After a maintenance renewal, we received a new key for the SLES subscription because our current subscription could no longer be activated with the existing key. With the new key we can now synchronize all SLES repos within the scope of the subscription again, but obviously all OES2018 repos are missing. I am sure that with the old key all OES2018 repos were listed and could be selected. Are we doing something wrong or does something have to be activated in addition to the new subscription key? Thanks for the support! Thomas Mit freundlichen Grüßen / Kind regards Thomas Weis NTW Netzwerk • Telekommunikation • Datentechnik Burghaldenstrasse 24 D-71336 Waiblingen

2 3

Uyuni 2022.10 is released!
by Julio Gonzalez 14 Oct '22

14 Oct '22

VERY IMPORTANT: 2022.10 requires special procedures for the upgrade from any previous version! Make sure you read the release notes for all the versions between the one you are using now, and 2022.10! We are happy to announce the availability of Uyuni 2022.10. Most openSUSE mirrors should already have 2022.10, 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.10, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Special instructions for the update, make sure you read them! - RHEL/Oracle Linux/AlmaLinux/Rocky Linux 9 as clients - Monitoring for Ubuntu 22.04 - pip support for the Salt Bundle - Apache exporter updated to version 0.11.0 for SUSE Linux Enterprise and openSUSE - Cobbler updated to version 3.3.3 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.10 As always, we hope you will enjoy Uyuni 2022.10 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

1 0

CentOS 7 channel selection issue
by Paul-Andre Panon 12 Oct '22

12 Oct '22

Hi, I've been running into an issue with our CentOS 7 clients. We didn't have this problem before but seem to have it with recent client additions. When trying to change the base and child channels for a CentOS 7 system, the change fails and corrupts the client repo config file at /etc/yum.repos.d/susemanager:channels.repo. The gpgkey= lines somehow have the non-Uyuni repo signing keys still in there, with the Uyuni key on a separate line immediately after. For example [susemanager:centos7-x86_64] name=CentOS 7 (x86_64) enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 file:///etc/pki/rpm-gpg/mgr-gpg-pub.key baseurl=https://carmd-nv-uyuni1.sierrawireless.local:443/rhn/manager/download/centos7-x86_64 susemanager_token=eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2OTUyNDgzNzEsImlhdCI6MTY2MzcxMjM3MSwibmJmIjoxNjYzNzEyMjUxLCJqdGkiOiI0UkhWYWUzU0VnTngwRk1yaXFsWG13Iiwib3JnIjoxLCJvbmx5Q2hhbm5lbHMiOlsiY2VudG9zNy14ODZfNjQiXX0.EoqL2bHAZ4li3FGsXuatKny5BU0qJ1aDbdJifTD_Gkw gpgcheck=1 repo_gpgcheck=1 type=rpm-md Instead that gpgkey line should just look like gpgkey=file:///etc/pki/rpm-gpg/mgr-gpg-pub.key It currently only seems to happen with the CentOS 7 clients. Is this a bug in a recent CentOS client update, or a database issue? Cheers, Paul-Andre Panon

2 3