September 2020 - ARCHIVED: Uyuni Users

[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 System ID: not incrementing since upgrade.
by Simon Avery 28 Sep '20

28 Sep '20

Hello, I have an unusual issue with Uyuni, which I upgraded last Thursday from 2020 07 to 09 using the "Minor" instructions here<:%20https:/www.uyuni-project.org/doc/2020.09/uyuni_upgrade_guide.pdf> The issue I have is that the "Uyuni System ID" is not incrementing after adding a new machine. This is preventing me adding new machines. If I add a new machine (Machine1) using the bootstrap method (Centos 8), it will add the machine correctly and on checking the Details tab, I can see it has Uyuni System ID: 1000010015 It behaves perfectly well and seems correctly registered with Uyuni. I then add another machine (Machine2) using the bootstrap method, which has a different hostname, mac, ip etc. Machine1 has now disappeared from Uyuni's server list. Machine2 is present and correct, but on checking, it is showing Uyuni System ID: 1000010015 So clearly the internal counter is somehow failing to increment and Machine2's details are overwriting Machine1's The previous 10 machines (possibly added before the upgrade) are all present and fine. Please advise, thank you. S

5 7

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

24 Sep '20

Hello everyone! We are happy to announce the immediate availability of Uyuni 2020.09 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2020.09, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Keep in mind Uyuni 2020.07 changed the base OS to openSUSE Leap 15.2, so a special procedure is needed if you are not upgrading from 2020.07 but from a previous version! Check the release notes and the documentation for all the details This is the list of highlights for this release: * Uyuni Hub XML-RPC API is now supported * Formula for peripheral server management (Technology Preview) * Maintenance windows * Monitoring reverse proxies * Added new type of "Virtual Host Manager": Nutanix AHV * Grafana 7.1.5 * New products enabled Please check the release notes for full details. We will also have Uyuni Community Hours this Friday 25th at 16.00 CEST to present Uyuni 2020.09 [1] 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.09 As always, we hope you will enjoy Uyuni 2020.09 and we invite everyone of you to send us your feedback [2] and of course your patches, if you can contribute. Happy hacking! [1] https://teams.microsoft.com/l/meetup-join/ 19%3Ameeting_ZmZmNzY5MjAtZGI2Mi00MDY1LWJiMTMtYjU3N2U0YmQxMmQz%40thread.v2/0? context=%7B%22Tid%22%3A%22f7a17af6-1c5c-4a36-aa8b- f5be247aa4ba%22%2C%22Oid%22%3A%2283d1ce03-a2c8-4530-8955-02fbc59cb7d6%22%7D Conference ID: 169 720 66# Dial-in numbers: https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d? id=16972066 [2] https://www.uyuni-project.org/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 9

[uyuni-users] Automatically accepting salt clients
by Simon Avery 24 Sep '20

24 Sep '20

Hi I'm wondering if it's possible to automatically accept new clients registered using the curl|bootstrap method? Currently, the clients register automatically and end up being held in a list by Uyuni. The bootstrap is executed automatically on new machine build or manually as I migrate machines over from our old Spacewalk instance. This list is viewable from the web interface under "Home/Overview" -> "Manage Pending Minions (1)" and allows me to manually approve new clients. I would like to bypass this step to allow for fully automated addition. Is this possible? The only method I can find is to crontab "salt-key -ay" every minute or so, which accepts all pending new clients. However, I feel I'm missing something obvious! Thank you S

2 2

[uyuni-users] Special update for CVE-2020-8028 (bsc#1175884)
by Julio González Gil 22 Sep '20

22 Sep '20

Dear lists, today we released an unscheduled maintenance update for CVE-2020-8028 (bsc#1175884), which is a security vulnerability of SUSE Manager and Uyuni Servers. The bug has been kept under embargo since it was reported to this day while we prepared a fix and coordinated the release. Only users that have shell access to the Uyuni server can exploit this vulnerability. This is not a common setup, shell access to the server should usually be restricted to the server administrators. In order to install this update please make sure you are on the most recent release (2020.07) and use the following commands on the Uyuni server: zypper addrepo https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… zypper refresh spacewalk-service stop zypper update spacewalk-java-lib spacewalk-java spacewalk-java-config spacewalk-java-postgresql spacewalk-taskomatic spacewalk-admin spacewalk-setup salt-netapi-client spacewalk-service start After services start again, the Salt API endpoint will be authenticated and encrypted. As the fix changes the way the Salt API endpoint is served, it is expected to break any third-party scripts or software that may rely on it. We will take this occasion to remind you that: - the Salt API endpoint configured by Uyuni at installation time is exclusively for internal Uyuni use and by default not exposed to the network. If your custom software depends on using the Salt API directly, you are relying on something not supported by Uyuni. - it is possible to define additional API endpoints, and secure them in a variety of ways, and those are fine for custom scripts. More information about how to configure those are available at: https://docs.saltstack.com/en/latest/ref/netapi/all/salt.netapi.rest_tornad… If applying the update is not readily feasible, we recommend to restrict shell access to the Uyuni Server to the minimum set of users who really need it - which is a standard, recommended security practice in any case. More information is available at: - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8028 - https://github.com/uyuni-project/uyuni/pull/2613 -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

4 10

[uyuni-users] Uyuni Community Hours 25.09.2020
by Pau Garcia 22 Sep '20

22 Sep '20

Hello After a Summer break, we are back with Uyuni Community Hours! Agenda: 1. What's new in Uyuni 2020.09 2. (get in touch with me if you want to present something!) Microsoft Teams meeting: Link to join: https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZmZmNzY5MjAtZGI2Mi00… Conference ID: 169 720 66# Dial-in numbers: https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=… Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager Phone: +1 385-666-5608 SUSE Software Solutions Spain

1 1

[uyuni-users] RE: Upgrade openSUSE Leap
by Haupt, Torsten 16 Sep '20

16 Sep '20

Hi, I tried it, but in the GUI I can't change the base channel to openSUSE Leap 15.2. In the dialog under SUSE-channels openSUSE Leap 15.1 is activated and under custom channels I see CentOS. I can't choose other base channels. And yes, there is an openSUSE 15.2 channel, created in the GUI, under admin | products. This channel is also synchronized. But I can't choose it as new base channel for the system. Torsten > -----Original Message----- > From: Flores, Javier-GMZ [mailto:Javier.Flores@gmz.migros.ch] > Sent: Tuesday, September 15, 2020 8:33 AM > To: Haupt, Torsten <Torsten.Haupt(a)lhw.mlu.sachsen-anhalt.de> > Subject: [EXTERN] AW: Upgrade openSUSE Leap > > Hi > > I usually first update to the latest packages of the current release, then attach > the channels of the new release and simply run "zypper dist-upgrade" on the > client. > > Regards, > Javier > > -----Ursprüngliche Nachricht----- > Von: Haupt, Torsten <Torsten.Haupt(a)lhw.mlu.sachsen-anhalt.de> > Gesendet: Tuesday, September 15, 2020 7:00 AM > An: uyuni-users(a)opensuse.org > Betreff: [uyuni-users] Upgrade openSUSE Leap > > Hi, > > what is the right way to upgrade openSUSE Leap 15.1 to 15.2 using Uyuni? > I mean a client, not the Uyuni server. > > Torsten > -- > To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org > To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

6 14

[uyuni-users] Clients not showing up in Systems list
by Len Ewen 15 Sep '20

15 Sep '20

I've got a freshly built openleap 15.2 server running 2020.07. When I try to install a client, the client shows up in Salt, which I accept, but the client never appears in the systems list. Any suggestions as to where I look to see what is going on? --------------- 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 9

[uyuni-users] Upgrade openSUSE Leap
by Haupt, Torsten 15 Sep '20

15 Sep '20

Hi, what is the right way to upgrade openSUSE Leap 15.1 to 15.2 using Uyuni? I mean a client, not the Uyuni server. Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 0

[uyuni-users] Check salt-ssh clients status through command line ?
by Bidault, Philippe 11 Sep '20

11 Sep '20

Hi all , I have noticed that Uyuni will silently fail to get the package information from a salt-ssh registered client if it get for example a ssh 'permission denied'. As far as I can see, the only way to detect such failures is to check the taskomatic logs and look for those messages: 2020-09-11 05:07:02,597 [DefaultQuartzScheduler_Worker-13] WARN com.suse.manager.webui.services.impl.SaltService - JsonParsingError({"_error":"Failed to return clean data","stderr":"root@my_server: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).\r\n","stdout":"","retcode":255,"id":"my_server","fun":"state.apply","jid":"20200911050701681150","_stamp":"2020-09-11T05:07:02.592894"}, No salt ssh return value, return code: 255) My idea is then to monitor the state of the VMs by executing the command "salt-ssh my_server test.ping", however I am unable to find the SSH private key files used by Uyuni. Somebody has an idea about where it could be find ? Or perhaps a better way to monitor those failures ? 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