- ARCHIVED: Uyuni Development

Moving config from susemanager.spec
by Stefan Bluhm 20 Jul '21

20 Jul '21

Hello, whilst cleaning up some more error messages, I came across this section in the susemanager.spec https://github.com/uyuni-project/uyuni/blob/master/susemanager/susemanager.… %posttrans # make sure our database will use correct encoding . /etc/sysconfig/postgresql if [ -z $POSTGRES_LANG ]; then grep "^POSTGRES_LANG" /etc/sysconfig/postgresql > /dev/null 2>&1 if [ $? = 0 ]; then sed -i -e "s/^POSTGRES_LANG.*$/POSTGRES_LANG=\"en_US.UTF-8\"/" /etc/sysconfig/postgresql else echo "POSTGRES_LANG=\"en_US.UTF-8\"" >> /etc/sysconfig/postgresql fi fi Can I move this to "/susemanager/bin/mgr-setup" or is it to clean some legacy installations? Best wishes, Stefan

2 1

Uyuni Community Hours
by Abid Mehmood 15 Jul '21

15 Jul '21

Hello, Time for another session! Agenda: 1. Rocky Linux 8 ( Julio) 2. Bootstrapping Ansible clients (Franky) 3. Q&A * Get in touch with the team if you want to present something! Abid ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_MTI5ZGEyNzItNDY4MC00…> Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=507f0242-e013-433a-…> ________________________________________________________________________________

1 0

Difference in py26-compat packages
by Stefan Bluhm 12 Jul '21

12 Jul '21

Hello, can anyone tell me the difference between these two packages: python2-tornado and py26-compat-tornado python2-msgpack and py26-compat-msgpack-python I noticed that py26-compat-salt requires the python2-XXX packages for build but requires py26-compat-XXX packages for runtime. This would require to maintain two packages for each of these cases. Best wishes, Stefan

2 1

Re: Where to find bootstrap logs
by Stefan Bluhm 12 Jul '21

12 Jul '21

Thank you both. the trace took me further. See some errors on accessing the CA. So some permission errors. I will look at them later. file_|-/etc/pki/ca-trust/source/anchors/RHN-ORG-TRUSTED-SSL-CERT_|-/etc/pki/ca-trust/source/anchors/RHN-ORG-TRUSTED-SSL-CERT_|-managed(retcode=2): Unable to manage file: none of the specified sources were found cmd_|-update-ca-certificates_|-/usr/bin/update-ca-trust extract_|-run(retcode=2): One or more requisite failed: certs./etc/pki/ca-trust/source/anchors/RHN-ORG-TRUSTED-SSL-CERT cmd_|-trust_res_gpg_key_|-rpm --import https://uyuni.example.com:443/pub/res-gpg-pubkey-0182b964.key_|-run(retcode…: Command "rpm --import https://uyuni.example.com:443/pub/res-gpg-pubkey-0182b964.key" run cmd_|-trust_suse_manager_tools_rhel_gpg_key_|-rpm --import https://uyuni.example.com:443/pub/sle12-gpg-pubkey-39db7c82.key_|-run(retco…: Command "rpm --import https://uyuni.example.com:443/pub/sle12-gpg-pubkey-39db7c82.key" run Also in /var/logs/salt/api 2021-07-12 14:34:33,890 [salt.roster :106 ][ERROR ][1895] Can't access roster for backend flat: Roster file "susemanager-roster-17133542272910374645.tmp" not found The "py26-compat-salt" package will need some fixing and testing for EL8 for different namings and impacts.... Tomcat is also empty. Seems like I have to revisit some file locations and permissions. I am now moving this thread over to uyuni-devel as this is not a usage question anymore. Best wishes, Stefan Von: "Victor Zhestkov" <Victor.Zhestkov(a)suse.com> An: "opensuse org" <opensuse.org(a)bluhm-de.com>, "Julio Gonzalez" <jgonzalez(a)suse.com> CC: "Victor Zhestkov" <Victor.Zhestkov(a)suse.com>, "users" <users(a)lists.uyuni-project.org>, "uyuni-users" <uyuni-users(a)opensuse.org> Gesendet: Montag, 12. Juli 2021 14:11:45 Betreff: Re: Where to find bootstrap logs Hi Stefan. Bootstrapping with web UI is performed with salt-ssh (even if you are bootstraping ordinary minion, not ssh one) through salt-api service. To find out exact error it's better to set logging level for salt master to trace: /etc/salt/master.d/logging.conf: log_level_logfile: trace Could be done with any conf file under /etc/salt/master.d/ no need to restart salt-master, but salt-api only. Unfortunately most of the messages required to debugging are visible it trace logging level only, but it's too noisy and log file is growing to fast. Regards, Victor On Mon, 2021-07-12 at 13:42 +0200, Stefan Bluhm wrote: Hello Julio, Server and client are both AlmaLinux 8. The py26 packages were not installed so I guess this is a missing dependency that needs fixing. I installed them, now the salt api log is empty and I am back to square 1: No log entries at all. a) What OS is installed at the client? Since py26 is mentioned, I guess CentOS6? AlmaLinux 8 b) How are you bootstrapping? WebUI? Script? WebUI (Systems --> Bootstrapping) c) What kind of client do you intend to bootstrap? SSH or regular salt minion? I actually don't know. I guess SSH as it mentions SSH on the page? Maybe here is the user error. I don't know anything about boot strapping. This is what I did: 1. Installed Uyuni. 2. Loaded the channels and created an activation key 3. Kickstarted an Alma Client. Now I am trying add the Alma Server to the Uyuni system management. I did nothing further on the client assuming the WebUI boot strapping is doing everything. Best wishes, Stefan ----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" < [ mailto:jgonzalez@suse.com | jgonzalez(a)suse.com ] > An: "Victor Zhestkov" < [ mailto:Victor.Zhestkov@suse.com | Victor.Zhestkov(a)suse.com ] >, "Stefan Bluhm" < [ mailto:opensuse.org@bluhm-de.com | opensuse.org(a)bluhm-de.com ] > CC: "users" < [ mailto:users@lists.uyuni-project.org | users(a)lists.uyuni-project.org ] >, "uyuni-users" < [ mailto:uyuni-users@opensuse.org | uyuni-users(a)opensuse.org ] > Gesendet: Montag, 12. Juli 2021 13:05:09 Betreff: Re: Where to find bootstrap logs On lunes, 12 de julio de 2021 10:07:13 (CEST) Stefan Bluhm wrote: BQ_BEGIN Thank you both! Julio, I added you to my linux god of the month list. I didn't realise "tail -f *" was possible. It would have saved me so much time in the past. there were no entries for "tail -f /var/log/rhn/*" But "tail -f /var/log/salt/*" gave in api ==> api <== 2021-07-12 10:02:17,312 [salt.utils.thin :289 ][WARNING ][1899] Module tornado is not a Python importable module with 2021-07-12 10:02:17,313 [salt.utils.thin :289 ][WARNING ][1899] Module msgpack is not a Python importable module with /usr/lib64/susemanager/py26-compat/msgpack 2021-07-12 10:02:17,364 [salt.utils.thin :282 ][WARNING ][1899] Module backports_abc configured with not a file or does not exist: /usr/lib/python2.7/site-packages/salt/ext/backports_abc.py 2021-07-12 10:02:17,365 [salt.utils.thin :303 ][ERROR ][1899] Missing dependencies for the alternative version in the external configuration: tornado, msgpack Our salt experts should have a look, but I wonder: a) What OS is installed at the client? Since py26 is mentioned, I guess CentOS6? b) How are you bootstrapping? WebUI? Script? c) What kind of client do you intend to bootstrap? SSH or regular salt minion? In any case, both directories are provided by the compat packages: m233:~ # rpm -qf /usr/lib64/susemanager/py26-compat/tornado py26-compat-tornado-4.2.1-53.2.uyuni1.x86_64 m233:~ # rpm -qf /usr/lib64/susemanager/py26-compat/msgpack py26-compat-msgpack-python-0.4.6-53.2.uyuni1.x86_64 Both should be installed, as dependencies for py26-compat-salt, which is part of the uyuni serve pattern. Do you have them installed? BQ_BEGIN So will chase up on those modules above. Best wishes, Stefan Von: "Victor Zhestkov" < [ mailto:Victor.Zhestkov@suse.com | Victor.Zhestkov(a)suse.com ] > An: "opensuse org" < [ mailto:opensuse.org@bluhm-de.com | opensuse.org(a)bluhm-de.com ] >, "Julio Gonzalez" < [ mailto:jgonzalez@suse.com | jgonzalez(a)suse.com ] > CC: "users" < [ mailto:users@lists.uyuni-project.org | users(a)lists.uyuni-project.org ] >, "uyuni-users" < [ mailto:uyuni-users@opensuse.org | uyuni-users(a)opensuse.org ] > Gesendet: Montag, 12. Juli 2021 09:58:14 Betreff: Re: Where to find bootstrap logs Hi Stefan. Please also check /var/log/salt/api. Regards, Victor On Mon, 2021-07-12 at 09:21 +0200, Stefan Bluhm wrote: Thank you Julio, I also expected a server error. But I do not see any relevant errors in the logs (or so I assume). find . -type f -newer /tmp/$$ # all files changed today ./tasko/sat/notifications-cleanup-bunch/notifications-cleanup_15359_out ./tasko/sat/mgr-sync-refresh-bunch/mgr-sync-refresh_16848_err ./tasko/sat/mgr-sync-refresh-bunch/mgr-sync-refresh_16848_out ./tasko/sat/channel-repodata-bunch/channel-repodata_17057_out ./search/rhn_search.log ./search/rhn_search_daemon.log ./rhn_taskomatic_daemon.log tomcat/local_access_log.2021-07-12.txt shows these consecutive lines: 192.168.0.152 - - [12/Jul/2021:07:33:06 +0200] "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 192.168.0.152 - - [12/Jul/2021:07:44:53 +0200] "GET /rhn/errors/500.jsp HTTP/1.1" 500 - /var/lib/pgsql/data/log/postgresql-Mon.log is empty. So I guess, I have to up the log level, right? Best wishes, Stefan ----- Ursprüngliche Mail ----- Von: "Julio Gonzalez" < [ mailto: [ mailto:jgonzalez@suse.com | jgonzalez(a)suse.com ] | [ mailto:jgonzalez@suse.com | jgonzalez(a)suse.com ] ] > An: "uyuni-users" < [ mailto: [ mailto:uyuni-users@opensuse.org | uyuni-users(a)opensuse.org ] | [ mailto:uyuni-users@opensuse.org | uyuni-users(a)opensuse.org ] ] >, "users" < [ mailto: [ mailto:users@lists.uyuni-project.org | users(a)lists.uyuni-project.org ] | [ mailto:users@lists.uyuni-project.org | users(a)lists.uyuni-project.org ] ] > CC: "Stefan Bluhm" < [ mailto: [ mailto:opensuse.org@bluhm-de.com | opensuse.org(a)bluhm-de.com ] | [ mailto:opensuse.org@bluhm-de.com | opensuse.org(a)bluhm-de.com ] ] > Gesendet: Montag, 12. Juli 2021 08:50:08 Betreff: Re: Where to find bootstrap logs On lunes, 12 de julio de 2021 7:48:43 (CEST) Stefan Bluhm wrote: BQ_BEGIN Hello, I seem to be blind or have lost my patience. When entering "host" (tried IP/hostname), "user"/"password", "activation key" and "Disable SSH.." under "Systems --> Bootstrapping" a blue info message appears "Your system is bootstrapping: waiting for a response..". After some long time, the bar changes to the red error bar saying: "Server error, please check log files.". Where are the logs for the bootstrap attempts? I claim, I searched "everywhere". In this case, this seems to be problem at the server, not at the client. /var/log/rhn at the server is the place where you need to start looking. Most likely there will be an ISE (Internal Server error) there. In some cases it could be interesting having a look at the tomcat log and PostgreSQL logs. BQ_BEGIN Thank you and best wishes, Stefan BQ_END BQ_END BQ_END BQ_END

2 2

Merging custom CentOS packages to Master
by Stefan Bluhm 07 Jul '21

07 Jul '21

Hello all, Next big activity is pushing the required CentOS 8 packages to the Uyuni Master branches. The distribution of packages to repositories on the Uyuni Server are: - Uyuni Master: 98 + Uyuni Master Other: 58 - New custom packages: 46 - EPEL: 34 - PowerTools: 50 - CentOS 8 BaseOS: 477 + CentOS 8 AppStream: 196 1) I would push my newly created custom packages including kits to "Uyuni Master Other". Are there any guidelines? Otherwise I would just split out the change log of the spec file and submit. 2) What do we do about the EPEL and PowerTools packages? I feel a bit uneasy of pushing 84 packages (+ probable build dependencies) to OPS. Especially when you consider that these packages need to be maintained and monitored for security fixes. 3) One more (not so pleasant) thought is the module system. Installation requires activation of 10 modules and deactivation of 2 more modules. If we go for loading all packages of point 2) into OBS, we might as well add the ones from the modules and create an Uyuni Server module (one per major release?). That would simplify the user experience and probably use the module system as intended (but kill maintainability...). Let me know your thoughts and ways to continue. Best wishes, Stefan

3 3

Uyuni talks at openSUSE Conference 2021
by Pau Garcia 25 Jun '21

25 Jun '21

Hi I gave a couple of talks at openSUSE Conference last week. Here are the links: * Uyuni, the movie Slide deck: https://www.slideshare.net/UyuniProject/uyuni-the-movie Video recording: https://youtu.be/wZxnmruV_Uo * Enabling new client operating systems in Uyuni Slide deck: https://www.slideshare.net/UyuniProject/enabling-new-client-operating-syste… Video recording: https://youtu.be/mX5XRI_l-1M Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager Engineering & Innovation SUSE Software Solutions Spain

1 0

Uyuni 2021.06 is released!
by Julio Gonzalez 24 Jun '21

24 Jun '21

We are happy to announce the immediate availability of Uyuni 2021.06 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.06, including the release notes, documentation, requirements and setup instructions. VERY IMPORTANT: Read the release notes. Uyuni 2021.06 will change the base OS for the Server and Proxy to openSUSE Leap 15.3 and some manual special steps are required. The upgrade is only possible if you are on 2020.07 or newer. This is the list of highlights for this release: * Salt 3002 * Base System Upgrade * PostgreSQL 13 * Missing openSUSE Leap 15.3 channels added to spacewalk-common-channels * Integration of Ansible into an Uyuni automation environment to protect customer investment and ease migration (Technology Preview) Please check the release notes for full details. Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2021.06 As always, we hope you will enjoy Uyuni 2021.06 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

Uyuni Community Hours
by Pau Garcia 09 Jun '21

09 Jun '21

Join us one more month to learn and discuss about Uyuni! The latest developments around Uyuni are presented and the community can ask question, provide feedback, request or suggest features or enhancements, etc to the Product Owner and members of the development team. Agenda will be published in the Uyuni wiki: https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours NB: Uyuni Community Hours are held every last Friday of the month, at 4pm CET. Meetings are recorded and published in the Uyuni YouTube channel: https://www.youtube.com/channel/UCB0SkZFAw9vPCFeUIYqZQ5A ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_MjNhOWQzOTktZTk0MS00…> Or call in (audio only) +34 917 94 59 77,,418209063#<tel:+34917945977,,418209063#> Spain, Madrid Phone Conference ID: 418 209 063# Find a local number<https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=…> | Reset PIN<https://mysettings.lync.com/pstnconferencing> Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=83d1ce03-a2c8-4530-…> ________________________________________________________________________________

1 0

Fix for a problem syncing Debian/Ubuntu client tools
by Julio Gonzalez 28 May '21

28 May '21

Hi, Thanks to a report from Markus Thum, we realized that the repository syncing scripts did not support DEB packages without a Maintainer field at the control file. This was never a problem because Debian and Ubuntu DEB packages always have this field (it is mandatory according to their policies). But the new "scap-security-guide-*" DEBs don't have this field at this moment. We intend to fix this in collaboration with the SLE package maintaners (as we just build the package for Ubuntu/Debian from their sources), but that is going to take some time, and it would require republishing the client tools for Uyuni. While this problem does not break the repository syncing scripts, it shows an error on-screen, or at the logs (that produces an email each time an automated sync is launched). For this reason we decided to use the Patch procedure to fix this issue at the server (in the end packages without the Maintaner field are valid [1]), instead of waiting until Uyuni 2021.06 is released. You can apply the patch by following the instructions at: https://www.uyuni-project.org/pages/patches.html#server Of course, the fix will be part of Uyuni 2021.06 as well, so it's not required if you don't manage Debian or Ubuntu clients. Best regards. [1] https://manpages.debian.org/buster/dpkg-dev/deb-control.5.en.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2021.05 is released!
by Julio Gonzalez 24 May '21

24 May '21

Hello everyone! We are happy to announce the immediate availability of Uyuni 2021.05 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.05, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Read the release notes. Depending on your current Uyuni version some more manual steps can be required to update the Server (for example if your current version is < 2021.05) This is the list of highlights for this release: - SLE Micro 5.0 and openSUSE MicroOS as clients - Deprecated products (RHEL6 and clones, Ubuntu16.04) - Prometheus TLS - Updated Prometheus - Migrate clients from openSUSE Leap to SUSE Linux Enterprise Server - Easier system group and configuration channel assignment - Enhanced CLM filter list - Notify beacon for DEB-based clients - Allow setting primary FQDN for the systems - Virtualization improvements - Custom data as pillar - Retracted patches - Client systems forwarded to SUSE Customer Center - Configuration state summary - Live patching made easy with filter templates - HTML documentation for the API - New API calls - spacecmd improvements - Activation key dropped from system details - Software Crashes (ABRT) dropped Please check the release notes for full details. 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 2021.05 As always, we hope you will enjoy Uyuni 2021.05 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