April 2020 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Monitoring with Prometheus and Grafana
by Martin Willisegger 23 Apr '20

23 Apr '20

Hello everyone I have just updated my older (4.0.x) uyuni installation on openSuSE Leap 15.1 to version 2020.04. Basically everything worked as before after that. I use the installation mainly for educational purposes, since we just bought a SuSE Manager license at work and I will have to familiarize myself with it in the future. I have now tried to set up the monitoring using this guide: https://www.uyuni-project.org/uyuni-docs/uyuni/administration/monitoring.ht… I tried to install the Prometheus service once via zypper and later also via the Web GUI. The installation worked with both variants, but Prometheus will no longer start if you enter the configuration as described in the manual. The problem seems to be this area: # Managed systems metrics: - job_name: 'mgr-clients' uyuni_sd_configs: - host: "http://server.url" username: "admin" password: "admin" Journalctl then shows the following error after a restart of Prometheus and the service dies immediately: Apr 22 22:21:11 uyuni systemd[1]: Started Monitoring system and time series database. -- Subject: Unit prometheus.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit prometheus.service has finished starting up. -- -- The start-up result is done. Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.282242749Z caller=main.go:302 msg="Starting Prometheus" version="(version=2.7.1, branch=non-git, revision=non-git)" Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.282475132Z caller=main.go:303 build_context="(go=go1.12.2, user=abuild@build30, date=20190506-21:40:46)" Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.282506478Z caller=main.go:304 host_details="(Linux 4.12.14-lp151.28.44-default #1 SMP Fri Mar 20 18:20:20 UTC 2020 (dbf1aea) x86_64 uyun> Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.282832865Z caller=main.go:305 fd_limits="(soft=1024, hard=4096)" Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.282976953Z caller=main.go:306 vm_limits="(soft=unlimited, hard=unlimited)" Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.283536813Z caller=main.go:620 msg="Starting TSDB ..." Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.283863869Z caller=repair.go:48 component=tsdb msg="found healthy block" mint=1587549831122 maxt=1587556800000 ulid=01E6GZSKYY5FKCBP0X6VR> Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.284036613Z caller=repair.go:48 component=tsdb msg="found healthy block" mint=1587556800000 maxt=1587564000000 ulid=01E6H6E9GFRTC0TK53Z3H> Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.28420424Z caller=repair.go:48 component=tsdb msg="found healthy block" mint=1587564000000 maxt=1587571200000 ulid=01E6HDA0Q73T9YBKBVM975> Apr 22 22:21:11 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:11.305763892Z caller=web.go:416 component=web msg="Start listening for connections" address=0.0.0.0:9090 Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.935791302Z caller=main.go:635 msg="TSDB started" Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.93611987Z caller=main.go:695 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.936572835Z caller=main.go:489 msg="Stopping scrape discovery manager..." Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.947640541Z caller=main.go:503 msg="Stopping notify discovery manager..." Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.947869093Z caller=main.go:525 msg="Stopping scrape manager..." Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948016593Z caller=main.go:499 msg="Notify discovery manager stopped" Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948172824Z caller=main.go:485 msg="Scrape discovery manager stopped" Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948311087Z caller=manager.go:736 component="rule manager" msg="Stopping rule manager..." Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.94844027Z caller=manager.go:742 component="rule manager" msg="Rule manager stopped" Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948608988Z caller=main.go:519 msg="Scrape manager stopped" Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948801003Z caller=notifier.go:521 component=notifier msg="Stopping notification manager..." Apr 22 22:21:12 uyuni prometheus[672]: level=info ts=2020-04-22T20:21:12.948936138Z caller=main.go:679 msg="Notifier manager stopped" Apr 22 22:21:12 uyuni prometheus[672]: level=error ts=2020-04-22T20:21:12.949071439Z caller=main.go:688 err="error loading config from \"/etc/prometheus/prometheus.yml\": couldn't load configuration (--config.file=\"/etc/prometheus/prometheus.yml\"): parsing YAML file /etc/prometheus/prometheus.yml: yaml: unmarshal errors:\n line 44: field uyuni_sd_configs not found in type config.plain" Apr 22 22:21:12 uyuni systemd[1]: prometheus.service: Main process exited, code=exited, status=1/FAILURE Apr 22 22:21:12 uyuni systemd[1]: prometheus.service: Unit entered failed state. Apr 22 22:21:12 uyuni systemd[1]: prometheus.service: Failed with result 'exit-code'. The problem seems to be here: YAML file /etc/prometheus/prometheus.yml: yaml: unmarshal errors:\n line 44: field uyuni_sd_configs not found in type config.plain Unfortunately I can't find any help on Google - it also seems to be a specific problem at uyuni, due to the name of the type Does anyone have any ideas? Best regards Martin Willisegger -- 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] Salt and delivering files
by Steve Moring 22 Apr '20

22 Apr '20

Needing a little hint. I'd like to deliver /etc/motd to clients I see https://www.uyuni-project.org/uyuni-docs/uyuni/salt/salt-states.html ...and pillars. Do I create a state channel or config channel? -- 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] Current release/list of releases
by Steve Moring 17 Apr '20

17 Apr '20

Hi, How does one figure out which release is currently installed. patterns-uyuni-4.0-400.9.1.uyunimaster refers to which release? -Steve -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 7

RE: [uyuni-users] Uyuni 2020.04 is released!
by Pau Garcia Quiles 17 Apr '20

17 Apr '20

Hello I have built unofficial Uyuni 2020.04 Server and Proxy VM appliances for KVM and Xen, VMware, Hyper-V, VirtualBox, AWS EC2, Azure, GCE and OpenStack. https://build.opensuse.org/project/show/home:pagarcia:Uyuni:2020.04 Direct download: https://build.opensuse.org/package/binaries/home:pagarcia:Uyuni:2020.04/Uyu… https://build.opensuse.org/package/binaries/home:pagarcia:Uyuni:2020.04/Uyu… Thank you Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain ________________________________ De: Julio Gonzalez Enviado: Jueves, 16 de Abril de 2020 13:13 Para: uyuni-announce(a)opensuse.org; uyuni-users(a)opensuse.org; uyuni-devel(a)opensuse.org Asunto: [uyuni-users] Uyuni 2020.04 is released! Hello everyone! We are happy to announce the immediate availability of Uyuni 2020.04 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2020.04, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: * Recurring actions * Bootstrapping Salt Clients with a Private SSH key (from API) * CentOS8 Content Lifecycle Management: Better Feedback with Appstreams * Automated Schema Database Upgrades and Failure Security Mechanism * Large Deployments Guide (draft) * Uyuni Hub documentation * Public Cloud QuickStart Guide (draft) * CaaSP Grafana Dashboads * Prometheus Federation Support in Formulas with Forms * Pre-configured default alerting rules * Prometheus Exporters for CentOS8 x86_64 * Node Exporter Updated to 0.18.1 * Virtualization: Management of storage pools 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.04 As always, we hope you will enjoy Uyuni 2020.04 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 1

[uyuni-users] Salt downgrade?
by Cristian Gherman 17 Apr '20

17 Apr '20

I see salt packages are downgraded from 2019.2.3 to 2019.2.0 in Uyuni 2020.04 in same stable repo? Why? 2020/03/20 03:33:15 -04:00 17/34 : salt-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 18/34 : salt-api-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 19/34 : salt-cloud-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 20/34 : salt-minion-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 21/34 : salt-proxy-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 22/34 : python2-salt-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 23/34 : salt-ssh-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 24/34 : salt-master-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:15 -04:00 25/34 : salt-standalone-formulas-configuration-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:16 -04:00 26/34 : salt-syndic-2019.2.3-17.1.uyuni.x86_64.rpm 2020/03/20 03:33:16 -04:00 28/34 : salt-doc-2019.2.3-17.1.uyuni.x86_64.rpm And today: 2020/04/16 15:14:23 -04:00 13/28 : salt-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:23 -04:00 14/28 : python2-uyuni-common-libs-4.1.4-2.1.uyuni.x86_64.rpm 2020/04/16 15:14:23 -04:00 15/28 : salt-cloud-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:23 -04:00 16/28 : salt-api-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 17/28 : python2-salt-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 18/28 : salt-minion-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 19/28 : salt-proxy-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 20/28 : salt-ssh-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 21/28 : salt-standalone-formulas-configuration-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 22/28 : salt-doc-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 23/28 : salt-syndic-2019.2.0-40.1.uyuni.x86_64.rpm 2020/04/16 15:14:24 -04:00 24/28 : spacewalk-check-4.1.5-2.1.uyuni.noarch.rpm 2020/04/16 15:14:24 -04:00 25/28 : salt-master-2019.2.0-40.1.uyuni.x86_64.rpm -- Cristian Gherman -- 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] Uyuni 2020.04 is released!
by Julio González Gil 16 Apr '20

16 Apr '20

Hello everyone! We are happy to announce the immediate availability of Uyuni 2020.04 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2020.04, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: * Recurring actions * Bootstrapping Salt Clients with a Private SSH key (from API) * CentOS8 Content Lifecycle Management: Better Feedback with Appstreams * Automated Schema Database Upgrades and Failure Security Mechanism * Large Deployments Guide (draft) * Uyuni Hub documentation * Public Cloud QuickStart Guide (draft) * CaaSP Grafana Dashboads * Prometheus Federation Support in Formulas with Forms * Pre-configured default alerting rules * Prometheus Exporters for CentOS8 x86_64 * Node Exporter Updated to 0.18.1 * Virtualization: Management of storage pools 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.04 As always, we hope you will enjoy Uyuni 2020.04 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

1 0

[uyuni-users] How to access Optional Channels from an SCC Product
by Tim Shaw 15 Apr '20

15 Apr '20

When a product is added from the SUSE Customer Centre in the setup wizard, channels are created and synced for all the mandatory channels associated with the product. However none of the optional channels listed are added or synced and there seems to be no ability to select from any of the optional channels available How can optional channels under a product be added as software channels in Uyuni? *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] Wrong data displayed
by Tobias Crefeld 10 Apr '20

10 Apr '20

Hi, after an accidental (rpm-) update to 2020.03 (with errors about a missing column) I rolled back the machine to an older snapshot before the update. Finally most things are running fine again but there are still some issues: 1.) The URI https://<FQDN>/rhn/manager/notification-messages shows a blank white "frame" (top bar and side bar are fine), although there should be more than 40 messages according to the "bell" in the top bar. Pressing the "bell" the tomcat log shows the following lines: "GET /rhn/manager/notification-messages HTTP/1.1" 200 34729 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "GET /rhn/manager/notification-messages/data-unread HTTP/1.1" 200 10089 (I stripped IP and time code) Calling /rhn/manager/notification-messages/data-unread directly delivers a JSON page with all unread notifications. 2.) One of the 3 servers (actually the first SLES machine that had been registered) in "System Overview" shows 30 Patches and 53 Packages. Triggering an Patch is executed without error but afterwards the "system overview" still shows the missing patches and packages. On the respective system calling "zypper up" shows "Nothing to do.". 3.) At the WebUI under Salt / Keys a blank white "frame" is shown, too. Under Salt / Formula Catalog a white "frame" with the text "Something wrong happened. Please reload the page. If the problem persist, please check log files". Tomcat-Logs show: "GET /rhn/manager/formula-catalog HTTP/1.1" 200 34636 "GET /rhn/manager/api/formula-catalog/data HTTP/1.1" 200 142 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 "POST /rhn/manager/frontend-log HTTP/1.1" 200 16 Again a direct call of the 2nd URI with the "api" delivers a JSON document with a list of the catalogs available. Any idea what is going wrong there (and how to fix it)? All pages worked fine in the beginning after the base installation of Uyuni (Uyuni 2020.01 on openSUSE 15.1) I wonder if Uyuni provides some tools for testing and/or aligning a system? Thanks in advance! Regards, Tobias. -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 3

[uyuni-users] Cobbler and Kickstart taskomatic errors
by Tim Shaw 08 Apr '20

08 Apr '20

Hello I have noticed that I have started to receive error emails when starting spacewalk services wjhich indicate that there is a problem with kickstart and cobbler. I cannot correlate this with any action I have taken recently - I moved to a third party SSL certificate a week or so ago but the errors started a while after that. I get emails saying: Taskomatic bunch cobbler-sync-bunch was scheduled to run within the cobbler-sync-default schedule. Subtask cobbler-sync failed. and Taskomatic bunch kickstartfile-sync-bunch was scheduled to run within the kickstartfile-sync-default schedule. Subtask kickstartfile-sync failed. Logfiles for both processes show: ERROR com.redhat.rhn.taskomatic.task.KickstartFileSyncTask - Stack trace:com.redhat.rhn.manager.kickstart.cobbler.NoCobblerTokenException: We had an error trying to login. ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - RuntimeExceptionError trying to sync to cobbler: We had an error trying to login. com.redhat.rhn.manager.kickstart.cobbler.NoCobblerTokenException: We had an error trying to login. It looks like taskomatic cannot login to perform its tasks - but I am not aware of what might have changed to cause this other than potentially this certificate change (which appears to work perfectly) - can anyone advise where to start looking? Many thanks 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

1 1

[uyuni-users] Salt + AD + sssd
by Crefeld, Tobias LKV Bayern e.V. 02 Apr '20

02 Apr '20

Hi, I'd like so setup our SLES-15 clients to use an active directory (Microsoft) for user authentication. I already have a SLES-15 machine that is running this configuration using sssd and it works fine. So there is a verified installation description for a manual setup available. Now I want to automate this configuration procedure. As far as I understood Uyuni is using Salt Formulas for these kind of configuration jobs (?). Looking at the opensuse-15.1 repositories (zypper se --type package formula) and at https://github.com/saltstack-formulas I haven't found anything to address this issue but maybe I just used the wrong search words. Any hints? Regards, Tobias. -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 3