May 2021 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

Config channels - how do they work?
by Simon Avery 18 May '21

18 May '21

Hello, I'm seeking clarity about Config channels. I've read the docs and been using them for a while, and whilst all the manual aspects work as I expect, the automation bits aren't. I've read the documentation but still have some questions. I'm not sure on whether this is a bug, or more likely, I'm misunderstanding or have misconfigured. Problem: I can see Uyuni regularly compares remote files to those in the config channels and reports versions, but even when a remote file is changed, it doesn't replace the remote file. Example: I have a file in a Uyuni "managed config channel" called "/root/myfile.txt". I push this to a remote client and it appears there. (Or a new vm is built and the file deployed when it's bootstrapped to uyuni) I then modify the file *on the remote client* In Uyuni, if I manually run "Show differences between profiled config files and deployed config files" for that server (or let Uyuni do its periodic check) it does not replace the remote file. Expectation: That Uyuni would diff the remote file and if it was different, would re-push a copy from central configuration. Because there is facility for Note: Uyuni is spotting the files have changed - on the System vm page: "Last Uyuni and System Comparison: 9 hours ago 30 of 31 files on the system were successfully compared with Uyuni-Managed files. [View Details<https://ata-oxy-uyuni01.atass.com/rhn/systems/details/history/Event.do?aid=…>] 4 of 30 files on the system differed from the Uyuni-Managed files." I don't have any State Channels configured - other than salt-minion as a remote client, I'm not doing anything Salty with Uyuni at all. Can anyone help me understand what's supposed to happen please, and how I can encourage Uyuni to force certain files? Thank you Simon

3 4

Re: SMDBA Tool does not clean up the backup archives
by Thomas Weis 17 May '21

17 May '21

Hi Jordi, it is the documentation from the Uyuni project site: https://www.uyuni-project.org/uyuni-docs/uyuni/administration/backup-restor… I configured all of them exactly as documented there, including the entry in /etc/cron.d/db-backup-mgr. @Michael Calmer the one and only entries in the daily log files are: "unexpected EOF on client connection with an open transaction" I think this is just an indication of the online status of the DB during the "hot backup"? Otherwise, log files and the WAL files in / var / spacewalk / db-backup are diligently created every day. The files are just simply not deleted @Silvio Moioli that's exactly what I assumed, it doesn't make sense to keep the WAL files until the Last Judgment. To make room temporarely, I deleted the oldest files from 2020 manually now. Regards Thomas > Am 17.05.2021 um 10:46 schrieb Jordi Massaguer Pla <jmassaguerpla(a)suse.de>: > > > On 5/14/21 6:56 PM, Thomas Weis wrote: >> Hi Jordi, >> >> Thank you for your answer. >> Yes, I expected that the smba tool would only archive a certain time frame. >> According to the documentation: "The smdba tool also manages your archives, keeping only the most recent backup, and the current archive of logs." >> Have I misinterpreted that and do I delete the superfluous archives manually or by script or does the smdba tool not do what it should do here? > > Can you do me a favor and point me to the documentation? I joined this teams some months ago and, among other things, I am taking care of this, so I don't know yet all the details, thus I am not sure if you refer to suse manager docs, uyuni wiki, smdba readme > > If you don't mind sending me a link to the docs where this is stated, you would save me some time to look everywhere ;) > > > Thanks in advance > > jordi > > > > -- > Jordi Massaguer Pla > Linux Engineer > SUSE Linux > https://www.suse.com >

1 0

SMDBA Tool does not clean up the backup archives
by Thomas Weis 17 May '21

17 May '21

Hello everybody, Since our initial installation of Uyuni, we have been making database backups with the smdba tool. We set up the backup exactly according to the information in the documentation. After the first manual backup, the automatic backups were activated via cron and work perfectly. Today we received a warning about insufficient storage space and found that the old archives in the DB backup directory / var / spacewalk / db-backup are obviously not to be deleted. All daily archives are available back to 09/20/2020. Where do I start looking for the cause? Many thanks for the support! best regards Thomas

4 4

Issue trying to share EPEL 8 repo between CentOS 8 and Alma 8
by Bidault, Philippe 14 May '21

14 May '21

Hi all, I am trying to use the EPEL 8 repository already in use by a CentOS 8 channel, on a new created channel for Alma 8. However no matter what, I have this error on a Alma 8 server while trying to install a package coming from EPEL 8 repo: # yum install screen AlmaLinux 8 AppStream (x86_64) 7.2 MB/s | 8.7 MB 00:01 EPEL 8 for AlmaLinux 8 (x86_64) 711 B/s | 251 B 00:00 Errors during downloading metadata for repository 'susemanager:epel8-alma8-x86_64': - Downloading successful, but checksum doesn't match. Calculated: b3dae961df1c6d9c7aeee6aa7e47da707b371f50(sha1) Expected: 66af4e77dffc81221d6dc1e600bb7b5f8d91c3bd(sha1) - Downloading successful, but checksum doesn't match. Calculated: cbf52120a8eea9bfbd9a049f73b3d56d855fbeff(sha1) Expected: 8507cfead7c1eff2c1a04b45d0981bef6baad476(sha1) Error: Failed to download metadata for repo 'susemanager:epel8-alma8-x86_64': Yum repo downloading error: Downloading error(s): repodata/primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/filelists.xml.gz - Cannot download, all mirrors were already tried without success I have absolutely no issue with this same repo but on a CentOS 8. Somebody with this same issue ? Am I doing something wrong or am I missing something ? Thanks ! Philippe. Philippe Bidault | Unix Engineer | Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com<https://www.getronics.com> [cid:3-lines_7512e235-163a-4853-8e4f-b0d4fc62ce73.png]<https://getronics.com/> Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/

1 1

Uyuni as simple Repository Server?
by Tobias Crefeld 14 May '21

14 May '21

Hi, I have several systems (SLES + opensuse) that have no access to the public internet but to our Uyuni system. Unfortunately we're not allowed to install a client software on these systems, so a regular system integration by Uyuni is not possible. On the other hand it is possible to edit the client's repository configuration ( /etc/zypp/repos.d/ manually. With a standard webserver that is regularly mirrored to a public repository this is no problem, but if I look at our typical salt clients I find baseurls like baseurl=https://HOST.DOMAIN.TLD:443/rhn/manager/download/sle-module-legacy15-sp1-updates-x86_64?eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2MzQ5ODE5NDAsImlhdCI6MTYwMzQ0NTk0MCwibmJmIjoxNjAzNDQ1ODIwLCJqdGkiOiIzQS1PbmpjanMtQXFETmZqVTJkTU93Iiwib3JnIjoxLCJvbmx5Q2hhbm5lbHMiOlsic2xlLW1vZHVsZS1sZWdhY3kxNS1zcDEtdXBkYXRlcy14ODZfNjQiXX0.H203CwoN5ns0YUnzZMmd Using these URL in a webbrowser returns 4xx - errors. Is there any way to provide the respective clients a standard path like http://download.opensuse.org/distribution/leap/15.2/repo/oss/ to the Uyuni server? Or is there any other way to provide Uyuni's repositories to these "clients" without installing special software at the client side? TIA! -- Gruss, Tobias Crefeld. xmpp (no email): crefeld(a)xabber.de

3 2

RE: Config channels - how do they work?
by Simon Avery 14 May '21

14 May '21

Thanks Stefan, it’s good to know that it can work! However, I’ve left the modified files in place on a target system and it hasn’t replaced them after three days, so it feels like it’s not going to. I wonder what’s not right on mine that is on yours? S From: Stefan Bluhm <stefan(a)bluhm-de.com> Sent: 13 May 2021 09:08 To: uyuni-users(a)opensuse.org; Simon Avery <Simon.Avery(a)atass-sports.co.uk> Subject: [EXTERNAL EMAIL] AW: Config channels - how do they work? Hey Simon, That is how it works for me. I see how many and what files changed including a diff per System. It does take some time to sync but you can force a refresh. Best wishes, Stefan Sent from a mobile device. ---- Simon Avery schrieb ---- Hello, I’m seeking clarity about Config channels. I’ve read the docs and been using them for a while, and whilst all the manual aspects work as I expect, the automation bits aren’t. I’ve read the documentation but still have some questions. I’m not sure on whether this is a bug, or more likely, I’m misunderstanding or have misconfigured. Problem: I can see Uyuni regularly compares remote files to those in the config channels and reports versions, but even when a remote file is changed, it doesn’t replace the remote file. Example: I have a file in a Uyuni “managed config channel” called “/root/myfile.txt”. I push this to a remote client and it appears there. (Or a new vm is built and the file deployed when it’s bootstrapped to uyuni) I then modify the file *on the remote client* In Uyuni, if I manually run “Show differences between profiled config files and deployed config files” for that server (or let Uyuni do its periodic check) it does not replace the remote file. Expectation: That Uyuni would diff the remote file and if it was different, would re-push a copy from central configuration. Because there is facility for Note: Uyuni is spotting the files have changed – on the System vm page: “Last Uyuni and System Comparison: 9 hours ago 30 of 31 files on the system were successfully compared with Uyuni-Managed files. [View Details<https://ata-oxy-uyuni01.atass.com/rhn/systems/details/history/Event.do?aid=…>] 4 of 30 files on the system differed from the Uyuni-Managed files.” I don’t have any State Channels configured – other than salt-minion as a remote client, I’m not doing anything Salty with Uyuni at all. Can anyone help me understand what’s supposed to happen please, and how I can encourage Uyuni to force certain files? Thank you Simon

1 1

aarch64 available for Server/Proxy for Uyuni Master
by Julio Gonzalez 14 May '21

14 May '21

Hi everyone, aarch64 is now enabled for the Master project [1]. Big thanks to Guillaume Gardet for helping us with the first steps and the initial testing! This means you can now install Uyuni Master Server on top of openSUSE Leap 15.2 aarch64 by following the instructions at https://www.uyuni-project.org/pages/devel-version.html The proxy can be installed by following the doc, and replacing x86_64 with aarch64 where appropriate (doc is not updated yet). Remember that Uyuni Master must not be used for production purposes!!!! Before we launch it as Stable, we want to gather some feedback from the community (as discussed during the last Community Hours). - If you give it a try and you don't find any issues, let's us know by replying to this email. - If you find issues, you can reply as well, but even a better alternative is creating an issue at https://github.com/uyuni-project/uyuni/issues Happy hacking! [1] https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Master -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 1

Uyuni Community Hours 28.05.2021
by Pau Garcia 09 May '21

09 May '21

Uyuni Community Hours are held every last Friday of the month, at 4pm CET. 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. Uyuni is the upstream project of SUSE Manager. ________________________________________________________________________________ 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_NDZmYWUyZWItMzhhOC00…> Or call in (audio only) +34 917 94 59 77,,946463263#<tel:+34917945977,,946463263#> Spain, Madrid Phone Conference ID: 946 463 263# 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

Autoyast complaining about unavailable Software
by Heiner Wulfhorst 06 May '21

06 May '21

Hi List, We have bare metal systems that have no network at boot/install time (LACP without fallback is used and we could not find any way to do PXE or DHCP at boot time). So we decided to use Uyuni integrated cobbler to create a bootable ISO for installation: #cobbler buildiso --distro=k8s-nodes-test:1:itmw-oss --airgapped --iso=/data/install_test_nodes_01_bios.iso --source=/var/autoinstall/SLE-15-SP2 We were able to boot from that image after switching from UEFI to legacy BIOS boot style. Autoyast starts but throws this errors: "could not set patterns: enhanced_base" "These packages cannot be found in the software repositories: autoyast2: The package is not available autoyast2-installation: The package is not available chrony-pool-empty: The package is not available tuned: The package is not available" And finally dies with: "... nothing provides /bin/sh needed by product:SLES-15.2..." I checked content of my ISO image and think it looks good, can also find the missing rpm files there: # find ./|grep -e chrony-pool-empty -e tuned -e bash-[0-9] ./Module-Server-Applications/noarch/tuned-2.10.0-11.3.2.noarch.rpm ./Module-Basesystem/noarch/chrony-pool-empty-3.2-9.12.1.noarch.rpm ./Module-Basesystem/x86_64/bash-4.4-9.10.1.x86_64.rpm I implemented it on a test system and was also able to find the rpms autoyast is missing. Why can't autoyast find these files? Must i reference them in my xml, in add-on section? If so, how? How can i create a bootable iso to install with autoyast without having a network connection? Or is there an easy way to create a boot iso that can activate LACP and then do a network install? Thanks, Heiner

1 0

New repository: Uyuni Contrib
by Jochen Breuer 04 May '21

04 May '21

Dear Uyuni community, I'm happy to let you know that we've release the Uyuni Contrib repository [0]. Uyuni Contrib contains tools that are not part of the core Uyuni system, mainly because they address a limited audience or are too experimental to be part of the main repository. This does not preclude their usefulness. So please use them with caution! Uyuni Contrib has currently two folder: * hubtools: Tools to install and configure SUSE Manager Hub. * uyuni-tools: Collection of useful Uyuni Tools. In order to use the tools with your Uyuni installation, you can simply download and extract the ZIP file [1] from GitHub to, for example, /opt. You Uyuni installation should have all dependencies needed to run all the tools. For more information, please check the corresponding README files: * https://github.com/uyuni-project/contrib/blob/main/README.md * https://github.com/uyuni-project/contrib/blob/main/hubtools/README.md * https://github.com/uyuni-project/contrib/blob/main/uyuni-tools/README.md Happy hacking! Jochen [0] https://github.com/uyuni-project/contrib/ [1] https://github.com/uyuni-project/contrib/archive/refs/heads/main.zip -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

1 0