July 2020 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Fresh Install uyuni 2020.05 Error generating bootstrap repo
by Thomas Weis 24 Aug '22

24 Aug '22

Hello everyone we are configuring a fresh installation of Uyuni 2020.05 After a successful reposync of SUSE Linux Enterprise Server 15 SP1 x86_64 we get an error message: Type: Creating Bootstrap Repository failed Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 show details said: ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' not found ERROR: package 'python3-rhnlib' not found ERROR: package 'spacewalk-check' not found ERROR: package 'spacewalk-client-setup' not found ERROR: package 'spacewalk-client-tools' not found ERROR: package 'python3-spacewalk-check' not found ERROR: package 'python3-spacewalk-client-setup' not found ERROR: package 'python3-spacewalk-client-tools' not found ERROR: package 'python3-uyuni-common-libs' not found ERROR: none of 'mgr-daemon', 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found ERROR: package 'python3-suseRegisterInfo' not found ERROR: package 'zypp-plugin-spacewalk' not found ERROR: package 'python3-zypp-plugin-spacewalk' not found The installation was error-free, we proceeded exactly according to the documentation. What is our mistake? thanks for suggestions Regards Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

[uyuni-users] Uyuni Community Hours 31.07.2020
by Pau Garcia 28 Aug '20

28 Aug '20

Hello Resending in a decent format since the mailing list management software seems to choke with Microsoft Teams appointments. We will be holding monthly Uyuni Community Hours on the last Friday of the month, as usual. Agenda: 1. Uyuni 2020.07. Now based on openSUSE Leap 15.2! 2. Salt module.run compatibility 3. Monitoring: exposing all your Prometheus metrics 4. Translations. How to make Uyuni available in your language. Link to join: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NTEzNGIzMDItMzUwMi00… Dial-in: Numbers: https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=… Conference ID: 620 373 916# Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain

3 2

[uyuni-users] Upgrading Clients to SLES 15 SP1
by Tobias Crefeld 06 Aug '20

06 Aug '20

Hi, is there an advice how to upgrade SLES 15 to SLES 15 SP1 (and later to SP2) by Uyuni (2020/01)? Searching at the web I only found a lot of hits for upgrading Uyuni itself (and the mail archive of this list is mainly delivering "Error 500" right now). At Uyuni's docs I find only some informations about X-upgrading SLES 12 to SLES 15. Of course I already added the respective channels at Admin / Setup Wizard / Products which got synchronized successfully in the meantime. How should I proceed? -- Gruss, Tobias Crefeld. xmpp (no email): crefeld(a)xabber.de -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 6

[uyuni-users] RE: Failed digest verification for bind-formula package during upgrade to 2020.07
by Bidault, Philippe 04 Aug '20

04 Aug '20

Well, no luck for the moment. How can I spot the failing mirror ? Regards, Philippe. From: Julio Gonzalez <jgonzalez(a)suse.com> Sent: viernes, 24 de julio de 2020 16:06 To: Bidault, Philippe <Philippe.Bidault(a)Getronics.com> Subject: Re: Failed digest verification for bind-formula package during upgrade to 2020.07 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. Looks to me like a problem with the mirror you are using and the metadata having one checksum while the actual packages have another checksum. Could be you just had bad luck and got in the middle of the mirror refresh? I'd try to clean with `zypper clean` the cache and launching again. If it still doesn't work, wait a little bit more. Otherwise I guess this will require a ticket to the openSUSE heroes so they disable the affected mirror. ________________________________ From: Bidault, Philippe <Philippe.Bidault(a)Getronics.com<mailto:Philippe.Bidault@Getronics.com>> Sent: Friday, July 24, 2020 4:01 PM To: uyuni-users(a)opensuse.org<mailto:uyuni-users@opensuse.org> <uyuni-users(a)opensuse.org<mailto:uyuni-users@opensuse.org>> Subject: [uyuni-users] Failed digest verification for bind-formula package during upgrade to 2020.07 Hi all, I have an error while executing the server-migrator.sh script: Retrieving: bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm .............................................................................................................[done] Warning: Digest verification failed for file 'bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm' [/var/tmp/AP_0xniEAF0/noarch/bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm] expected 87d9f5828518a721a98b7ba47234af28578e9c71ddaa4ba2e91d5490f1396b60 but got e3a476a93dfada74ef4cd863bd023efe9cd1c00101e98246d091a6c8d2d8fb2d Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum 'e3a4..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [e3a4/...? shows all options] (discard): discard Package bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch (Uyuni Server Stable) seems to be corrupted during transfer. Do you want to retry retrieval? Abort, retry, ignore? [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. I guess that this is something that needs to be fixed at the repository level ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com<mailto:Philippe.Bidault@Getronics.com> | W. www.getronics.com<http://www.getronics.com> [cid:image001.png@01D661DC.4B604CB0]<http://www.getronics.com/> [cid:image002.png@01D661DC.4B604CB0]<https://www.linkedin.com/company/2077785> [cid:image003.png@01D661DC.4B604CB0] <https://twitter.com/Getronics> [cid:image004.png@01D661DC.4B604CB0] <https://www.youtube.com/user/getronicsonline?feature=results_main> sign-info 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/

2 10

[uyuni-users] Probelm syncing Debian repos
by Tim Shaw 30 Jul '20

30 Jul '20

Hello Version: 2020.05 I newly created some Debian 9 repos using spacewalk-common-channels and when syncing for the first time get the following in the logs 11:01:41 ====================================== 11:01:41 | Channel: debian-9-pool-amd64-uyuni 11:01:41 ====================================== 11:01:41 Sync of channel started. 11:01:41 Plugin error: Package index checksum failure Generating bootstrap repos for all available products which had changes. Nothing to do. 11:01:41 Total time: 0:00:00 The url for the repo looks correct as it points to http://deb.debian.org/debian/dists/stretch/main/binary-amd64/ which appears to contain package lists. The published md5 checksum is apparently correct The only repo which did sync properly was the Security updates repo at http://security-cdn.debian.org/debian-security/dists/stretch/updates/main/b… I'm aware that Debian 9 has recently gone EOL although LTS continues to end June 2022 - could this have something to do with it or is there something broken ? regards T *Please note I am not normally in the office on Mondays or Fridays* ___________________________________________________________ TIM SHAW - Deputy Director - Network Services Medical Sciences Division - University of Oxford email : tim.shaw(a)medsci.ox.ac.uk tel : +44 (0)1865 289480 -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 1

[uyuni-users] IMPORTANT: Do not update Uyuni 2020.07 for now. Problems in some download mirrors
by Julio González Gil 29 Jul '20

29 Jul '20

Hi everyone. Thanks to Philippe Bidault, we realized that there is some problems with some of the mirrors where Uyuni is hosted, and for some reasons some of them still have 2020.06 and not 2020.07. Since zypper does not force using the same mirror for all downloads (in the end it calles the mirrordirector at download.opensuse.org) it could very well that you get the metadata from an outdated mirror and the packages from an updated mirror, and you see failures such as: > "Warning: Digest verification failed for file 'bind- formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm' > [/var/tmp/AP_0xbYw8c1/noarch/bind- formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm] > expected 87d9f5828518a721a98b7ba47234af28578e9c71ddaa4ba2e91d5490f1396b60 > but got e3a476a93dfada74ef4cd863bd023efe9cd1c00101e98246d091a6c8d2d8fb2d" We are already in contact with the openSUSE heroes so the problem can be solved, but in the meantime we recommend you wait before ugrading. We will keep you updated so you can proceed with the upgrade as soon as the problem is fixed. NOTE: A workaround is now posted at the uyuni-users mailing lists (basically using https://paste.opensuse.org/69951052 to replace the content on the migration script), but we DO NOT RECOMMEND you follow it unless you already started the upgrade and you have a backup. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 2

[uyuni-users] Virtual Host Manager API?
by Doug Whitfield 29 Jul '20

29 Jul '20

I assume the answer is no, since I don't see anything in the documentation, but is there any sort of API or extension framework for VHMs? There are other cloud providers other than the ones that have VHM (Rackspace, Digital Ocean, Alibaba, etc.). It would be good to be able to support those providers. Salt supports Rackspace as a first class citizen, and I have seen people using Salt with DO. The ability is not really the issue. In fact, I don't have an immediate need. I am giving a presentation to customers on Uyuni and I know some of these customers are using other cloud providers, so I would like to be prepared when the question comes up. Obviously, if the question comes up about Rackspace or DO I have answers, but I don't know all of the cloud providers all of our customers are using, so if I could point them to an API or extension framework for building their own, that would be ideal. Thanks! Doug Whitfield | Enterprise Architect, OpenLogic<https://www.openlogic.com/?utm_leadsource=email-signature&utm_source=outloo…> Perforce Software<http://www.perforce.com/?utm_leadsource=email-signature&utm_source=outlook-…> P: +1 800.487.3217 <tel:> Visit us on: LinkedIn<https://www.linkedin.com/company/perforce?utm_leadsource=email-signature&ut…> | Twitter<https://twitter.com/perforce?utm_leadsource=email-signature&utm_source=outl…> | Facebook<https://www.facebook.com/perforce/?utm_leadsource=email-signature&utm_sourc…> | YouTube<https://www.youtube.com/user/perforcesoftware?utm_leadsource=email-signatur…> Join Us! OpenLogic's Virtual User Conference September 16, 2020 | SAVE THE DATE<https://www.openlogic.com/open-at-home> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

2 1

[uyuni-users] Sync error channel uyuni-proxy-stable-leap-151-x86_64
by Bidault, Philippe 29 Jul '20

29 Jul '20

Hi all, Since the availability of Uyuni 2020.07, the sync of the repo uyuni-proxy-stable-leap-151-x86_64 fail with checksum errors: 2020/07/27 22:01:02 -00:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'uyuni-proxy-stable-leap-151-x86_64', '--type', 'yum', '--non-interactive'] 2020/07/27 22:01:02 -00:00 Sync of channel started. 2020/07/27 22:01:05 -00:00 Repo URL: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… 2020/07/27 22:01:05 -00:00 Packages in repo: 80 2020/07/27 22:01:08 -00:00 Packages already synced: 0 2020/07/27 22:01:08 -00:00 Packages to sync: 80 2020/07/27 22:01:09 -00:00 New packages to download: 72 2020/07/27 22:01:09 -00:00 Downloading packages: 2020/07/27 22:01:09 -00:00 1/72 : Uyuni-Proxy-release-2020.07-86.3.uyuni.x86_64.rpm 2020/07/27 22:01:09 -00:00 2/72 : jabberd-db-2.7.0-3.2.uyuni.x86_64.rpm 2020/07/27 22:01:09 -00:00 3/72 : jabberd-sqlite-2.7.0-3.2.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 4/72 : libgsasl-lang-1.8.0-1.6.uyuni.noarch.rpm 2020/07/27 22:01:10 -00:00 5/72 : jabberd-2.7.0-3.2.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 6/72 : libgsasl7-1.8.0-1.6.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 7/72 : golang-github-boynux-squid_exporter-1.6-3.12.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 8/72 : libntlm0-1.4-1.4.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 9/72 : libudns0-0.4-0.9.8.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 10/72 : mgr-cfg-4.1.2-1.1.uyuni.noarch.rpm 2020/07/27 22:01:10 -00:00 11/72 : mgr-cfg-actions-4.1.2-1.1.uyuni.noarch.rpm 2020/07/27 22:01:10 -00:00 12/72 : mgr-cfg-client-4.1.2-1.1.uyuni.noarch.rpm 2020/07/27 22:01:10 -00:00 13/72 : golang-github-lusitaniae-apache_exporter-0.7.0-2.7.uyuni.x86_64.rpm 2020/07/27 22:01:10 -00:00 ERROR: Download failed: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… - Target file isn't valid. Checksum should be d70f0b78f80d7d2484f5001933bb97b9bff19098a1ce5838c5b0906c4ff10bda (sha256).. Retrying... 2020/07/27 22:01:10 -00:00 14/72 : mgr-cfg-management-4.1.2-1.1.uyuni.noarch.rpm 2020/07/27 22:01:10 -00:00 ERROR: Download failed: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… - Target file isn't valid. Checksum should be c762844e0c805ce598ce66358b6b9aade509dec88e1f111a340d9d5a5a5215b1 (sha256).. Retrying... 2020/07/27 22:01:10 -00:00 15/72 : mgr-osad-4.1.3-1.1.uyuni.noarch.rpm ……. 2020/07/27 22:01:14 -00:00 Package batch #1 of 4 completed... 2020/07/27 22:01:14 -00:00 Importing packages finished. 2020/07/27 22:01:14 -00:00 2020/07/27 22:01:14 -00:00 Linking packages to the channel. 2020/07/27 22:01:16 -00:00 Unexpected error: <class 'spacewalk.server.importlib.importLib.InvalidPackageError'> 2020/07/27 22:01:16 -00:00 Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 590, in sync ret = self.import_packages(plugin, data['id'], url, is_non_local_repo) File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 1096, in import_packages importer.run() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/importLib.py", line 775, in run self.submit() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/packageImport.py", line 126, in submit self.backend.lookupPackages(self.batch, self.checksums) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 822, in lookupPackages raise_with_tb(not_found[0], not_found[1]) File "/usr/lib/python3.6/site-packages/uyuni/common/usix.py", line 77, in raise_with_tb raise value File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 814, in lookupPackages self.__lookupObjectCollection([package], 'rhnPackage') File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2490, in __lookupObjectCollection raise InvalidPackageError(object, "Could not find object %s in table %s" % (object, tableName)) spacewalk.server.importlib.importLib.InvalidPackageError: Could not find object [<<class 'spacewalk.server.importlib.importLib.IncompletePackage'> instance; attributes={'package_id': None, 'name': 'Uyuni-Proxy-release', 'epoch': None, 'version': '2020.07', 'release': '86.3.uyuni', 'arch': 'x86_64', 'org_id': 1, 'package_size': None, 'last_modified': None, 'md5sum': None, 'channels': {104: 'uyuni-proxy-stable-leap-151-x86_64'}, 'checksum_list': None, 'checksum': 'be45e52976929284ef3a9f8fb3511695581565a0cb88627b0f75fbb3a192fbb4', 'checksum_type': 'sha256', 'checksums': {'sha256': 'be45e52976929284ef3a9f8fb3511695581565a0cb88627b0f75fbb3a192fbb4'}, 'name_id': 53074, 'evr_id': 85894, 'package_arch_id': 120, 'nevra_id': 3195 I guess that this is “normal”, the packages 2020.06 and 2020.07 being mixed in the same mirrors ? Anyway, aesthetically speaking I guess that we do not want that 😊 Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> 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/

3 5

[uyuni-users] Uyuni Community Hours 31.07.2020
by Pau Garcia 24 Jul '20

24 Jul '20

Agenda 1. Uyuni 2020.07. Now based on openSUSE Leap 15.2! 2. Salt module.run compatibility 3. Monitoring: exposing all your Prometheus metrics 4. Translations. How to make Uyuni available in your language. ________________________________________________________________________________ Join Microsoft Teams Meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_NTEzNGIzMDItMzUwMi00…> +34 917 94 59 77<tel:+34%20917%2094%2059%2077,,620373916#> Spain, Madrid (Toll) Conference ID: 620 373 916# Local numbers<https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=…> | Reset PIN<https://mysettings.lync.com/pstnconferencing> | Learn more about Teams<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=83d1ce03-a2c8-4530-…> ________________________________________________________________________________

1 0

[uyuni-users] Uyuni 2020.07 is released!
by Julio González Gil 24 Jul '20

24 Jul '20

Hello everyone! We are happy to announce the immediate availability of Uyuni 2020.07 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2020.07, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Keep in mind Uyuni 2020.07 changes the base OS to openSUSE Leap 15.2, so a special procedure is needed for this upgrade! Check the release notes and the documentation for all the details This is the list of highlights for this release: * Salt 3000.0 * New "mgrcompat.module_run" custom compatibility state for Salt is available for registered systems. * PostgreSQL 12 * Base System Upgrade * New products enabled * Ubuntu 20.04 LTS * hwdata vendor change for openSUSE Leap 15.1 clients 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 2020.07 As always, we hope you will enjoy Uyuni 2020.07 and 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

2 2

[uyuni-users] Failed digest verification for bind-formula package during upgrade to 2020.07
by Bidault, Philippe 24 Jul '20

24 Jul '20

Hi all, I have an error while executing the server-migrator.sh script: Retrieving: bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm .............................................................................................................[done] Warning: Digest verification failed for file 'bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm' [/var/tmp/AP_0xniEAF0/noarch/bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch.rpm] expected 87d9f5828518a721a98b7ba47234af28578e9c71ddaa4ba2e91d5490f1396b60 but got e3a476a93dfada74ef4cd863bd023efe9cd1c00101e98246d091a6c8d2d8fb2d Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum 'e3a4..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [e3a4/...? shows all options] (discard): discard Package bind-formula-0.1.1573049925.b509ada-1.1.uyuni.noarch (Uyuni Server Stable) seems to be corrupted during transfer. Do you want to retry retrieval? Abort, retry, ignore? [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. I guess that this is something that needs to be fixed at the repository level ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> 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 0

[uyuni-users] Package being kept-back while upgrading from 2020.05 to 2020.06
by Bidault, Philippe 20 Jul '20

20 Jul '20

Hi all, This is like a dejá-vu of my previous upgrade from 2020.04 to 2020.05 😊 I have packages being kept-back while upgrading the packages: uyuni:~ # zypper up Retrieving repository 'Main Update Repository' metadata ....................................................................................................................[done] Building repository 'Main Update Repository' cache .........................................................................................................................[done] Loading repository data... Reading installed packages... The following 3 package updates will NOT be installed: libntlm0 lucene Uyuni-Server-release The following product update will NOT be installed: "Uyuni Server" Nothing to do. Is this expected ? Do I have to upgrade libntlm0 and Uyuni-Server-release by hand (zypper up libntlm0 Uyuni-Server-release) ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> 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/

2 5

[uyuni-users] Centos 6 and Oracle Linux 6
by Len Ewen 15 Jul '20

15 Jul '20

I am getting an error where it cannot find the ssl certificate even though it is in the bootstrap file. Oracle Linux 7 and Centos 7 install fine, but C6 and OL6 just freak out with the install. Is there some sort of magic I am missing to get C6 and OL6 to install properly? --------------- Len Ewen Systems Administrator 1 Information Technology University of Indianapolis (317) 788-3362 [image: UIndyIT.jpg] Confidentiality Notice: This communication and/or its content are for the sole use of the intended recipient, and may be privileged, confidential, or otherwise protected from disclosure by law. If you are not the intended recipient, please notify the sender and then delete all copies of it. Unless you are the intended recipient, your use or dissemination of the information contained in this communication may be illegal.

2 11

[uyuni-users] UUID and Uyuni
by Len Ewen 14 Jul '20

14 Jul '20

How does the UUID relate in the grand scheme of things in uyuni? I have a set of machines with the same UUID beause they are just VM clones. They are the only thing that is the same between images that I can discrene as being similar. When I try to add them they don't add into Uyuni correctly, swapping machines in and out as to which is showing at any time. The name might be different from IP address. What do I do, because changing the UUID on all my machines isn't happening. --------------- Len Ewen Systems Administrator 1 Information Technology University of Indianapolis (317) 788-3362 [image: UIndyIT.jpg] Confidentiality Notice: This communication and/or its content are for the sole use of the intended recipient, and may be privileged, confidential, or otherwise protected from disclosure by law. If you are not the intended recipient, please notify the sender and then delete all copies of it. Unless you are the intended recipient, your use or dissemination of the information contained in this communication may be illegal.

2 7

[uyuni-users] Problem importing CentOS 7 errata
by Beddingfield, Allen 14 Jul '20

14 Jul '20

I'm using 2020.06, and having an issue with importing CentOS 7 errata, using the cent-errata.sh method described in the documentation. When running the script, I receive the following error: INFO: Server is running API version 23 INFO: API version 23 is supported INFO: Authentication successful INFO: User has administrator access to this server INFO: Loading errata XML INFO: Loading Red Hat OVAL XML INFO: Getting server inventory INFO: Checking for unpublished errata Fault returned from XML RPC Server, fault code -1: redstone.xmlrpc.XmlRpcFault: Could not find method: listUnpublishedErrata in class: com.redhat.rhn.frontend.xmlrpc.errata.ErrataHandler with params: [com.redhat.rhn.domain.user.legacy.UserImpl] Any suggestions or assistance would be appreciated. Thanks. Allen B. -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 2

[uyuni-users] CentOS 8
by Huber, Peter 13 Jul '20

13 Jul '20

Hi, I have enrolled a centos 8 client. This client is not reinstalled, running in production for months and was never connected to our old spacewalk-system. I onboarded the client in the following way: cd /etc/yum.repos.d/ wget https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… yum install salt salt-minion cd /etc/salt/minion.d vi <hostaname>.conf master: ymaster-server> server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation_key: "1-centos8-x86_64" systemctl restart salt-minion systemctl enable salt-minion Webgui Salt => Keys, accept the key. Everything seems fine, but verifying this, shows a problem, I don't understand. yum check on the centos 8 client shows that all repositories are listed more than once. In /etc/yum.repo.d is only the susemanager repo, I have moved all other repos or disabled them. Patching this client does not work. After uninstalling salt and salt-minion, deleting the centos 8 server from uyuni this problem does not disappear. I removed all salt config files I could find. Now I have only one repofile in /etc/yum.repos.d, called CentOS-Base.repo yum check shows: Repository BaseOS is listed more than once in the configuration The server has no connection to the uyuni server and have really no idea what happed. Starting up this centos 8 client from a backup, shows that this problem appears after onboarding to uyuni. Any idea what went wrong? Thank you, Peter

2 2

[uyuni-users] spacewalk-common-channels
by Huber, Peter 13 Jul '20

13 Jul '20

Till now I managed to setup a uyuni server with two clients, one CentOS7 and one CentOS8. Everything is working as expected. I imported the channels via spacewalk-common-channels, e.g. spacewalk-common-channels -v -u admin -p <password> -a x86_64 -k unlimited 'centos7*' This worked in the same way as on our spacewalk server. Now I want to add some additional channels / repos in the same way and I got an error message: spacewalk-common-channels -v -u admin -p <password> -a x86_64 -k unlimited 'oraclelinux7*' Connecting to http://localhost/rpc/api Error: redstone.xmlrpc.XmlRpcFault: Either the password or username is incorrect. The password and the username is correct, I can login on the website with these credentials. I few days ago I used this to add a lot of channels/repos, what can be wrong? Any idea? Thank you, Peter -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

[uyuni-users] Upgrade registered Uyuni client from 15.1 to 15.2
by Bidault, Philippe 08 Jul '20

08 Jul '20

Hi all, I have seen documentation were the zypper repo file needs to be modified by hand to upgrade from Leap 15.1 to 15.2, and was now wondering, how the upgrade could be done on a registered Uyuni client ? Just by modifying the registered repo from the Uyuni web console does the trick ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> 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/

3 5

[uyuni-users] Re-registration of system with the same minion-id results in unmanagable system
by Mattias Giese 06 Jul '20

06 Jul '20

Heya, running Uyuni 2020.04 we encounter the following issue: If a user 'recycles' a system (through reprovisioning) the following happens: 1) We do not explicitly remove the current system profile in Uyuni nor remove the minion from salt 2) The system will be reprovisioned through our internal deployment system 3) After successful provisioning, we bootstrap the host with the same minion-id The result: The already existing system profile is not updated. Crucial information (like the dbus/systemd machine-id) is not refreshed in the profile leading to 'interesting' errors like these: ``` local: Data failed to compile: ---------- Specified SLS packages.packages_b60982e0e0334b5baffb24ca15e2b98a in saltenv base is not available on the salt master or through a configured fileserver ---------- Specified SLS custom.custom_b60982e0e0334b5baffb24ca15e2b98a in saltenv base is not available on the salt master or through a configured fileserver ``` This is happening because Uyuni is still using the machine-id of the previously deployed system for the generation of salt states. I raised the Taskomatic log level to debug in the hopes of seeing 'something' [TM], but grepping these logs using the machine-ids/hostnames didn't help me either. It seems as if Uyuni is simply skipping the bootstrap/registration procedure if the minion-id is already existing. There does not seem to be the possibility to 'force' a re-registration. So, my question to the Uyuni devs would be: Is the only way to work around this the complete deletion of the system profile or is there a magic flag/configuration setting hidden somewhere that i could specify? Regards, Mattias

2 2

[uyuni-users] Channel subscription after registering
by Huber, Peter 06 Jul '20

06 Jul '20

Hello, we are on a process to migrate our old spacewalk installation to uyuni or foreman. At the moment we are evaluating uyuni against foreman/katello. Till now a lot of things are working fine, but I found one thing, I don't understand. I configured all Centos 7 and Centos 8 channels and they are updated daily, this part is working fine. Now I want to subscribe a Centos test system. I do so by editing a salt config file in this way: master: <our uyuni server name> server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos8-x86_64" After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server? Thank you, Peter

5 13