- ARCHIVED: Uyuni Users

A fix for using HTTP proxies for repository synced is now released
by Julio Gonzalez 21 Jul '22

21 Jul '22

The fix requires two things: - Uyuni 2022.06 - The latest python3-urlgrabber from openSUSE Leap 15.4 The issue is being tracked at https://github.com/uyuni-project/uyuni/issues/4850 Special thanks to Dan Holstad, hbrown-uiowa, phibid and SpeedBlack for the report, and to Dominik Wombacher and Pablo Suárez for the fix. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Re: Error trying to bootstrap / register / onboard sles15sp3 salt client/minion
by Heiner W. 15 Jul '22

15 Jul '22

Hi List, here's some additional Information regarding my problem ("Error registering minion id: dehwllhdb21") What confuses me the most: Uyuni integrated salt master is able to work with said client/minion: # salt dehwllhdb21 cmd.run date dehwllhdb21: Thu Jul 14 09:37:22 CEST 2022 # salt dehwllhdb21 grains.items|wc -l 10118 # salt dehwllhdb21 grains.items|grep -A1 'id:' gid: 0 id: dehwllhdb21 lsb_distrib_id: SLES machine_id: a0a85c7a8e4c611fa66868da62cfc837 pid: 5881 server_id: 444072978 uid: 0 uuid: 0a024321-7508-5d5c-8f34-dc250ec0c11e What i already tried: I removed any salt rpm and config from client several times before each bootstrap retry: # zypper remove -y venv-salt-minion salt* # rm -rf /etc/venv-salt-minion* /etc/salt* Also regenerated system uid: # rm /etc/machine-id /var/lib/dbus/machine-id # dbus-uuidgen --ensure # systemd-machine-id-setup ... and rebooted the client os. I tried bootstrapping with new venv salt and also the old salt-minion packages. I even tried using another network interface on my client, with another ip, net, route to uyuni. Why can't uyuni register the client (get its data/grains) but directly using salt as root in bash from uyuni seems to work great? What else could i try? Thanks, Heiner

3 5

Where is mgr-bootstrap on a containerized proxy?
by Paul-Andre Panon 14 Jul '22

14 Jul '22

After some brow sweat figuring out that a firewalld IP range overlap between zone sources was breaking routing for a containerized proxy, I'm ready to try to follow up with setting up some bootstrap scripts on the proxy. However I can't seem to find mgr-bootstrap to do so because it doesn't appear to be in the container host path. How does one generate bootstrap scripts on a containerized proxy? Thanks Paul-Andre Panon

2 9

Spacewalk add channel has failed
by Martin Willisegger 12 Jul '22

12 Jul '22

Hello list Currently I cannot attach a specific channel for opensuse Leap 15.4 to Uyuni. I get the following error message: uyuni:~ # spacewalk-common-channels -a x86_64 opensuse_leap15_4-sle-updates SUSE Manager username: admin SUSE Manager password: Base channel 'openSUSE Leap 15.4 (x86_64)' - exists WARNING: opensuse_leap15_4-x86_64-sle-updates: redstone.xmlrpc.XmlRpcFault: The channel name 'Update repository with updates from SUSE Linux Enterprise 15 (x86_64)' is already in use, please enter a different name I think there is a conflict with the existing subchannel from Leap 15.3: opensuse_leap15_3-x86_64-sle-updates However, this repo is needed for 15.3 and 15.4. What possibility do i have to import and attach this channel for 15.4 anyway? Best regards Martin

1 0

Patch for Uyuni 2022.06
by Julio Gonzalez 06 Jul '22

06 Jul '22

Hello! Several users syncing openSUSE Leap 15.3/15.4 and/or the SUSE PackageHub reported that they are getting the following error running reposync from CLI, or at the WebUI notifications area: 2022/07/05 09:22:01 +02:00 Importing packages to DB: 2022/07/05 09:22:02 +02:00 'rpm.hdr' object has no attribute 'get' Please note that this bug does **not** prevent syncing other packages, it just means that the package `kicad-packages3D` version `5.1.8-bp154.1.18` failed to sync due to the bug. So it wont be available for Uyuniu clients, as it won't be synced at the server. Other than that the reposync will work just as usual. If automated syncing is for the affected channels is enabled, then you will also get notifications at the UI (the "bell" icon). A patch for Uyuni 2022.06 to fix both problems was just published, in case you do not want to wait for Uyuni 2022.07 (it will be part of that release as well). You can apply the patch by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are using Uyuni 2022.05 or older: make sure you update to 2022.06, and remember 2022.06 changes the base OS to openSUSE Leap 15.4, so you need to follow a special procedure (check the release notes). Thank to all users that reported the issue, and specially to Jonathan Müller (LordofAgents) for providing the information about the affected package. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

How to mirror/sync repos of type yast
by Heiner Wulfhorst 04 Jul '22

04 Jul '22

Hi List, i need to sync a HPE Foundation Repo into my CLM: https://update1.linux.hpe.com/repo/hpe-foundation/2.4.3/Suse/SLES15-SP3/ Unfortunately it seems to have yast structure: https://en.opensuse.org/openSUSE:Standards_YaST2_Repository_Metadata#Reposi… How can I mirror it into uyuni? Configuring it as yum type repo produces this error when trying to sync: *# spacewalk-repo-sync --type yum --channel hpe-foundation-workaround* 16:52:20 ====================================== 16:52:20 | Channel: hpe-foundation-workaround 16:52:20 ====================================== 16:52:20 Sync of channel started. Retrieving repository 'hpe-foundation-workaround' metadata ......................................................................................................................[done] Building repository 'hpe-foundation-workaround' cache ...........................................................................................................................[done] All repositories have been refreshed. 16:52:24 Unexpected error: <class 'FileNotFoundError'> 16:52:24 Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 610, in sync repo_checksum_type = plugin.get_md_checksum_type() File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/repo_plugins/yum_src.py", line 750, in get_md_checksum_type infile = fileutils.decompress_open(repomd_path) File "/usr/lib/python3.6/site-packages/uyuni/common/fileutils.py", line 521, in decompress_open file_obj = codecs.open(filename, 'r', encoding="utf8") File "/usr/lib64/python3.6/codecs.py", line 897, in open file = builtins.open(filename, mode, buffering) *FileNotFoundError: [Errno 2] No such file or directory: '/var/cache/rhn/reposync/1/hpe_foundation_workaround_repo/var/cache/zypp/raw/hpe-foundation-workaround/repodata/repomd.xml'* 16:52:24 Total time: 0:00:04 Thanks, BR, Heiner

3 4

Re: Uyuni 2022.06 is released!
by Julio Gonzalez 27 Jun '22

27 Jun '22

On lunes, 27 de junio de 2022 17:37:49 (CEST) Michele Bussolotto wrote: > > "In the Uyuni Server Web UI, navigate to proxy system's details page, > > click > > the Reactivation subtab. Click Generate New Key to generate a reactivation > > key." > > > > Is this really necessary ? I understand that we don't need to re-register > > the proxy. Just selecting the 15.4 repos and executing on the proxy > > 'zypper > > dup --allow-vendor-change' is enough, correct ? > > Correct, reactivation is no longer required. Thanks for noticing! @Philippe, can you maybe prepare a PR for the doc? It's quite easy, actually, the file is at https://github.com/uyuni-project/uyuni-docs/blob/master/modules/installatio… > ________________________________________ > From: Julio Gonzalez > Sent: Monday, June 27, 2022 5:27 PM > To: General discussion related to the openSUSE Uyuni project; > announce(a)lists.uyuni-project.org; devel(a)lists.uyuni-project.org; Bidault, > Philippe; Michele Bussolotto Subject: Re: Uyuni 2022.06 is released! > > > I can't tell for sure. > > @Michele? > > If it's not needed, then we should remove it from the doc. > > On lunes, 27 de junio de 2022 16:13:08 (CEST) Bidault, Philippe wrote: > > Hi Julio, > > > > Thanks for this ! Uyuni server upgraded, so far so good. > > > > However, I am still confused with the Proxy upgrade procedure > > (https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrad > > e > > /proxy-uyuni.html): > > > > "In the Uyuni Server Web UI, navigate to proxy system's details page, > > click > > the Reactivation subtab. Click Generate New Key to generate a reactivation > > key." > > > > Is this really necessary ? I understand that we don't need to re-register > > the proxy. Just selecting the 15.4 repos and executing on the proxy > > 'zypper > > dup --allow-vendor-change' is enough, correct ? > > > > Regards, > > Philippe. > > > > > > > > Philippe Bidault | Unix Engineer | Getronics > > > > M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.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: www.getronics.com/legal and further details of how we > > treat your personal data can be found in our privacy policy > > <www.getronics.com/policy-pages/corporate-policy-legal-disclaimer> > > -----Original Message----- > > From: Julio Gonzalez via Uyuni Users <users(a)lists.uyuni-project.org> > > Sent: 27 June 2022 09:59 > > To: announce(a)lists.uyuni-project.org; users(a)lists.uyuni-project.org; > > devel(a)lists.uyuni-project.org Cc: Julio Gonzalez <jgonzalez(a)suse.com> > > Subject: Uyuni 2022.06 is released! > > > > CAUTION: This email originated from outside of the organization. Do not > > click links or open attachments unless you recognize the sender and know > > the content is safe. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 1

Uyuni 2022.06 is released!
by Julio Gonzalez 27 Jun '22

27 Jun '22

VERY IMPORTANT: Uyuni 2022.06 switches the base OS for the Server and the Proxy to openSUSE Leap 15.4. Make sure you read the release notes before updating! We are happy to announce the immediate availability of Uyuni 2022.06. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.06, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Upgrade notes (read them carefully!) - Base system upgrade to openSUSE Leap 15.4 - PostgreSQL 14 - Salt 3004 - New products enabled 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 2022.06 As always, we hope you will enjoy Uyuni 2022.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

3 5

Re: [EXTERNAL] Re: Uyuni 2022.06 is released!
by Allen Beddingfield 27 Jun '22

27 Jun '22

We really need a well-documented and support way to progress from one version to another, without jumping straight to the current version, for those who get behind. I know there used to be an archive of each version out there that one could manually point to for accomplishing this. Does that still exist? -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu ________________________________ From: Julio Gonzalez via Uyuni Users Sent: Monday, June 27, 2022 8:41 AM To: General discussion related to the openSUSE Uyuni project; Simon Avery Cc: Julio Gonzalez Subject: [EXTERNAL] Re: Uyuni 2022.06 is released! Needless to say, you should not leave Uyuni without updates for a year, so ideally everyone should be already on 2022.05 or, at least, something newer than 2021.06 :-) If someone is on 2021.05 or earlier, updating could work, but it's not supported. Hope it helps. > Or should I follow the minor update procedure to go from 05 to 06 before > doing the major update procedure? > > Thanks, > > Simon > > -----Original Message----- > From: Julio Gonzalez via Uyuni Users <users(a)lists.uyuni-project.org> > Sent: 27 June 2022 08:59 > To: announce(a)lists.uyuni-project.org; users(a)lists.uyuni-project.org; > devel(a)lists.uyuni-project.org Cc: Julio Gonzalez <jgonzalez(a)suse.com> > Subject: [EXTERNAL EMAIL] Uyuni 2022.06 is released! > > VERY IMPORTANT: Uyuni 2022.06 switches the base OS for the Server and the > Proxy to openSUSE Leap 15.4. Make sure you read the release notes before > updating! > > We are happy to announce the immediate availability of Uyuni 2022.06. > > At https://www.uyuni-project.org/pages/stable-version.html you will find all > the resources you need to start working with Uyuni 2022.06, including the > release notes, documentation, requirements and setup instructions. > > This is the list of highlights for this release: > > - Upgrade notes (read them carefully!) > - Base system upgrade to openSUSE Leap 15.4 > - PostgreSQL 14 > - Salt 3004 > - New products enabled > > 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 2022.06 > > As always, we hope you will enjoy Uyuni 2022.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 -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 1

Problem setting up an Uyuni Proxy
by Paul-Andre Panon 17 Jun '22

17 Jun '22

I'm trying to set up an Uyuni proxy (using the proxy pattern) . It's a bit of an unusual configuration: 1. Uyuni server is a different domain 2. Have network connectivity but not DNS resolution 3. Application level firewall in between to networks 4. Certificates are signed by a separate internal Intermediate [+root] CA The networks will eventually get more integrated, but to get around 1 & 2, the proxy is in the server's host file, and the server and internal CA are in the proxy's host file. This seems to work well enough to get the proxy system registered as a minion/client with the Uyuni server. However, once I've created the cert for the proxy, when trying to run configure-proxy.sh, we get Requesting certificate from server. [1/20] ... Requesting certificate from server. [20/20] Certificate not received from server. Exit. /etc/sysconfig/rhn/systemid:1: parser error : Document is empty ^ unable to parse /etc/sysconfig/rhn/systemid SUSE Manager Parent [Uyuni_server.FQDNl]: Using CA Chain (from /etc/sysconfig/rhn/up2date): /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT HTTP Proxy []: Traceback email []: <removed spammer bait> You will now need to either generate or import an SSL certificate. This SSL certificate will allow client systems to connect to this Uyuni Proxy securely. Refer to the Uyuni Proxy Installation Guide for more information. Do you want to import existing certificates? [y/N]: y Path to CA SSL certificate: []: /root/ssl-build/RHN-ORG-TRUSTED-SSL-CERT Path to the Proxy Server's SSL key: []: /root/ssl-build/<proxy>.key Path to the Proxy Server's SSL certificate: []: /root/ssl-build/<proxy>.crt Installing SSL certificates: XXX: User postgres does not exist XXX: Group postgres does not exist cp: '/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT' and '/etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT' are the same file WARNING: upon deactivation attempt: unknown error - <Fault -12: 'redstone.xmlrpc.XmlRpcFault: method invalid param'> There was a problem activating the SUSE Manager Proxy entitlement: WARNING: upon deactivation attempt: unknown error - <Fault -12: 'redstone.xmlrpc.XmlRpcFault: method invalid param'> Proxy activation failed! Installation interrupted. WARNING: upon deactivation attempt: unknown error - <Fault -12: 'redstone.xmlrpc.XmlRpcFault: method invalid param'> There were some answers you had to enter manually. Would you like to have written those into file formatted as answers file? [Y/n]: y Writing proxy-answers.txt.u4qp3 I'm hoping the first few errors aren't too much of an issue. I'm not sure what I would have missed, step wise, to lead to the SUSE Manager Proxy entitlement errors. I didn't find anything obvious through a google search for those errors. The CA certs have been installed on the proxy, so if I try to use wget to fetch a file from the pub folder on the Uyuni server, it has no apparent problems with cert verification. I appreciate any suggestions or pointers you can offer. Thanks, Paul-Andre Panon

2 3