- ARCHIVED: Uyuni Users

[uyuni-users] Changing the from name in the Daily Status reports
by Simon Avery 24 Aug '20

24 Aug '20

Hello, Not the most critical of problems, but one that niggles each day. By default, Uyuni sends scheduled emails, like the Daily Status report, addressed with the FROM field as: "SUSE Manager" As the only Suse box in our organisation is the one Uyuni runs on, this is confusing to our users and disbalances the cosmic harmony of things being 'right'. I'd like to change this, perhaps to "Uyuni Server Manager". I can't seem to find documentation relating to changing this. Is it possible, please? Thanks, S

1 0

[uyuni-users] Check of packages via GPG keys now enable on Uyuni 2020.07 ?
by Bidault, Philippe 12 Aug '20

12 Aug '20

Hi all, I have noticed that "gpgcheck" parameter is now set to 1 in the susemanager:channels.repo repo client configuration. I have compared with servers registered before the upgrade to 2020.07, and GPG check was deactivated. Do you know why this change ? Is there a way to deactivate it again, or perhaps automatically import the GPG keys while registering the server in Uyuni ? 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] Removal of Ubuntu erratas in Uyuni
by Bidault, Philippe 11 Aug '20

11 Aug '20

Hi all, I have noticed that the CVE ID were truncated, importing them from the philicious script (https://github.com/philicious/spacewalk-scripts/blob/master/errata-import.py) Truncated because of the regexp limitation "CVE = "(?P<cve>CVE-\d{4}-\d{4})". I have modified it to accept 5 digits ( CVE = "(?P<cve>CVE-\d{4}-\d{5} ), but to be able to import them again, I would need to remove all the erratas from the Ubuntu repositories. Is there an easy way to do it ? 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 2

[uyuni-users] Apply Salt states upon registration
by Javier.Flores＠gmz.migros.ch 11 Aug '20

11 Aug '20

Hi I have state channels I would like to assign and apply to any new system that registers with Uyuni. Adding the state channels to the activation key is not enough. The state channels will be assigned, however they will not be automatically applied. As a workaround I added this to the boostrap.sh: sleep 60 && salt-call state.apply & Is there a more elegant way to achieve this? Regards, Javier

2 2

[uyuni-users] Error installing Uyuni server
by Len Ewen 10 Aug '20

10 Aug '20

I am installing the new 2020.07 on a brand new SUSE box and when I got to the install phase I am getting : Problem: nothing provides postgresql12 needed by spacewalk-postgresql-4.1.3-1.4.uyuni.noarch Detailed information: patterns-uyuni_server-2020.07-1.1.uyuni.x86_64 requires spacewalk-postgresql, but this requirement cannot be provided nothing provides postgresql12 needed by spacewalk-postgresql-4.1.3-1.4.uyuni.noarch I can't seem to figure out a way around this, I don't want to break postgres and end up in dependency hell, so has anyone seen this and has a work around? --------------- 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.

3 12

[uyuni-users] Problem running remote commands with Centos 8
by Simon Avery 10 Aug '20

10 Aug '20

Hello, Spacewalk orphan looking for new home here. New Leap 15.2 and Uyuni 2020.07 install. On bootstrapping a Centos 8 client, I hit some snags initially, and needed to install salt-minion on the client, which in turn needed a new repo adding. yum install https://repo.saltstack.com/py3/redhat/salt-py3-repo-latest.el8.noarch.rpm yum install salt-minion This installs salt-minion 3001-1.el8 plus dependencies. This allowed me to bootstrap through the Uyuni web interface and add the client successfully using the salt method. However, when running a remote command, such as "touch /tmp/i_exist.txt" (actual path doesn't matter), this fails with stderr: /bin/sh: /tmp/__salt.tmp.jir6xlhr.sh: Permission denied Googling tells me this is a salt error rather than a Uyuni one, but as Uyuni set up salt-minion I'm hoping to gain a solution here. Can anyone point me in the right direction please? Thanks

3 9

[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