- ARCHIVED: Uyuni Users

AW: Salt-Minion doesn't work after migration of system
by Crefeld, Tobias LKV Bayern e.V. 14 Apr '22

14 Apr '22

Hi, the error message is a little misleading as we don't run multiple masters. Actually the moved systems didn't have access to 4505/tcp and 4506/tcp of the Uyuni system due to the firewall setup. After adding the respective rules to the firewall, the error messages disappeared and system management works as usual. Regards, Tobias Crefeld. -----Ursprüngliche Nachricht----- Von: Crefeld, Tobias LKV Bayern e.V. Gesendet: Montag, 11. April 2022 10:45 we had to move several SLES15 systems to another network behind a firewall. Therefore we changed the respective files ifcfg-eth0, route and hosts and reloaded wicked. Access to repositories works fine but the service salt-minion shows: "Error while bringing up minion for multi-master. Is master at lkv-srvapp39.lkvbay.net responding?" (lkv-srvapp39 is the only Uyuni system)

1 0

Installed products - can this be changed?
by Tim Shaw 12 Apr '22

12 Apr '22

After running a product migration dry run on a SLES systsem in Uyuni 2022.02 I discovered that the "Installed Products" for that server bow displays the version which would have been installed had the migration actually been performed. I assume something went wrong in the restoration of the object to the state which it was in before the product migration dry run was performed Is there a way to correct the value of "Installed products" for a system using some command line tool? Or should I blow this system away and re register it? Thanks T *Please note I am now working part-time - Tuesdays and Wednesday only* ___________________________________________________________ TIM SHAW - MSD IT Systems & Network Services Medical Sciences Division - University of Oxford email : tim.shaw(a)medsci.ox.ac.uk tel : +44 (0)1865 289480

3 2

Re: Problem deleting systems from Uyuni 2022.03 (and probably 2022.02 as well before upgrading)
by Paul-Andre Panon 12 Apr '22

12 Apr '22

P.S. We’re seeing similar errors in the taskomatic log 2022-04-08 12:44:00,035 [DefaultQuartzScheduler_Worker-12] ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - re-throwing exception since we havent yet. 2022-04-08 12:44:00,035 [DefaultQuartzScheduler_Worker-12] ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - Executing a task threw an exception: com.redhat.rhn.manager.kickstart.cobbler.NoCobblerTokenException 2022-04-08 12:44:00,035 [DefaultQuartzScheduler_Worker-12] ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - Message: We had an error trying to login. 2022-04-08 12:44:00,035 [DefaultQuartzScheduler_Worker-12] ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - Cause: redstone.xmlrpc.XmlRpcFault: <class 'cobbler.cexceptions.CX'>:'login failed (taskomatic_user)' 2022-04-08 12:44:00,035 [DefaultQuartzScheduler_Worker-12] ERROR com.redhat.rhn.taskomatic.task.CobblerSyncTask - Stack trace:com.redhat.rhn.manager.kickstart.cobbler.NoCobblerTokenException: We had an error trying to login. at com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand.login(CobblerLoginCommand.java:56) at com.redhat.rhn.frontend.integration.IntegrationService.authorize(IntegrationService.java:113) at com.redhat.rhn.frontend.integration.IntegrationService.getAuthToken(IntegrationService.java:66) at com.redhat.rhn.manager.kickstart.cobbler.CobblerCommand.<init>(CobblerCommand.java:60) at com.redhat.rhn.manager.kickstart.cobbler.CobblerCommand.<init>(CobblerCommand.java:81) at com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand.<init>(CobblerDistroSyncCommand.java:47) at com.redhat.rhn.taskomatic.task.CobblerSyncTask.execute(CobblerSyncTask.java:85) at com.redhat.rhn.taskomatic.task.RhnJavaJob.execute(RhnJavaJob.java:89) at com.redhat.rhn.taskomatic.TaskoJob.execute(TaskoJob.java:158) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) Caused by: redstone.xmlrpc.XmlRpcFault: <class 'cobbler.cexceptions.CX'>:'login failed (taskomatic_user)' at redstone.xmlrpc.XmlRpcClient.handleResponse(XmlRpcClient.java:444) at redstone.xmlrpc.XmlRpcClient.endCall(XmlRpcClient.java:376) at redstone.xmlrpc.XmlRpcClient.invoke(XmlRpcClient.java:165) at com.redhat.rhn.manager.kickstart.cobbler.CobblerXMLRPCHelper.invokeMethod(CobblerXMLRPCHelper.java:69) at com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand.login(CobblerLoginCommand.java:51) ... 10 more Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

3 5

Salt-Minion doesn't work after migration of system
by Crefeld, Tobias LKV Bayern e.V. 11 Apr '22

11 Apr '22

Hi, we had to move several SLES15 systems to another network behind a firewall. Therefore we changed the respective files ifcfg-eth0, route and hosts and reloaded wicked. Access to repositories works fine but the service salt-minion shows: Error while bringing up minion for multi-master. Is master at lkv-srvapp39.lkvbay.net responding? (lkv-srvapp39 is the only Uyuni system) Any idea? Uyuni is release 2021.06. We used the workaround that Julio Gonzalez described at 01.04.22 and applied the patches of the salt packages only at the Uyuni system. Gruß, Tobias Crefeld.

1 0

Problem deleting systems from Uyuni 2022.03 (and probably 2022.02 as well before upgrading)
by Paul-Andre Panon 08 Apr '22

08 Apr '22

Hi, I looked in the last few months of the archive but couldn't see anything regarding this. My apologies if I missed it somehow. We're having strange behaviour in the GUI where trying to delete systems is failing. We've had this problem with different admin accounts: organization admins, Uyuni admins, admin accounts that are AD-integrated through PAM, the initial local admin account. We've enabled Duo multi-factor authentication but also had this problem before adding MFA. In all cases Uyuni fails to delete the system. After Confirming System Profile deletion, we first get a popup indicating Cleanup timed out. Please check if the machine is reachable. in the case of one system that had already been taken offline, but after indicating the profile should be deleted without cleanup (or without that first popup if we try to delete a system that is online) we get a follow-up error: Server error, please check log files.. Other operations work fine against systems: updating packages, rebooting systems, etc. We just can't delete systems. If we switch to the Admin menu to go look at the tomcat log, we see a notice: System profile 1000010001 could not be deleted. In the "tomcat" /var/log/rhn/rhn_web_ui.log log file, we see the errors: 2022-04-08 12:30:48,726 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-14] WARN com.suse.manager.webui.services.impl.SaltService - Got no result for state.apply on minion CARMD-EX-DWsbx4.sierrawireless.local (minion did not respond in time) 2022-04-08 12:30:50,542 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-9] ERROR com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand - XmlRpcFault while logging in. most likely user doesn't have permissions. redstone.xmlrpc.XmlRpcFault: <class 'cobbler.cexceptions.CX'>:'login failed (<myaccount>)' at redstone.xmlrpc.XmlRpcClient.handleResponse(XmlRpcClient.java:444) at redstone.xmlrpc.XmlRpcClient.endCall(XmlRpcClient.java:376) at redstone.xmlrpc.XmlRpcClient.invoke(XmlRpcClient.java:165) at com.redhat.rhn.manager.kickstart.cobbler.CobblerXMLRPCHelper.invokeMethod(CobblerXMLRPCHelper.java:69) at com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand.login(CobblerLoginCommand.java:51) at com.redhat.rhn.frontend.integration.IntegrationService.authorize(IntegrationService.java:113) at com.redhat.rhn.frontend.integration.IntegrationService.getAuthToken(IntegrationService.java:66) at com.redhat.rhn.manager.kickstart.cobbler.CobblerCommand.<init>(CobblerCommand.java:66) at com.redhat.rhn.manager.kickstart.cobbler.CobblerSystemRemoveCommand.<init>(CobblerSystemRemoveCommand.java:37) at com.redhat.rhn.manager.system.SystemManager.deleteServer(SystemManager.java:725) at com.redhat.rhn.manager.system.SystemManager.deleteServer(SystemManager.java:704) at com.suse.manager.webui.controllers.SystemsController.delete(SystemsController.java:218) at com.suse.manager.webui.utils.SparkApplicationHelper.lambda$withUser$1(SparkApplicationHelper.java:88) at spark.RouteImpl$1.handle(RouteImpl.java:72) at spark.http.matching.Routes.execute(Routes.java:61) at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:130) at spark.servlet.SparkFilter.doFilter(SparkFilter.java:173) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.AuthFilter.doFilter(AuthFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:142) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:58) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter.doFilter(LocalizedEnvironmentFilter.java:69) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.EnvironmentFilter.doFilter(EnvironmentFilter.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.SessionFilter.doFilter(SessionFilter.java:55) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:97) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:432) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1591) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:829) 2022-04-08 12:30:50,543 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-9] ERROR com.redhat.rhn.frontend.servlets.SessionFilter - Error during transaction. Rolling back com.redhat.rhn.manager.kickstart.cobbler.NoCobblerTokenException: We had an error trying to login. at com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand.login(CobblerLoginCommand.java:56) at com.redhat.rhn.frontend.integration.IntegrationService.authorize(IntegrationService.java:113) at com.redhat.rhn.frontend.integration.IntegrationService.getAuthToken(IntegrationService.java:66) at com.redhat.rhn.manager.kickstart.cobbler.CobblerCommand.<init>(CobblerCommand.java:66) at com.redhat.rhn.manager.kickstart.cobbler.CobblerSystemRemoveCommand.<init>(CobblerSystemRemoveCommand.java:37) at com.redhat.rhn.manager.system.SystemManager.deleteServer(SystemManager.java:725) at com.redhat.rhn.manager.system.SystemManager.deleteServer(SystemManager.java:704) at com.suse.manager.webui.controllers.SystemsController.delete(SystemsController.java:218) at com.suse.manager.webui.utils.SparkApplicationHelper.lambda$withUser$1(SparkApplicationHelper.java:88) at spark.RouteImpl$1.handle(RouteImpl.java:72) at spark.http.matching.Routes.execute(Routes.java:61) at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:130) at spark.servlet.SparkFilter.doFilter(SparkFilter.java:173) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.AuthFilter.doFilter(AuthFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:142) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:58) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter.doFilter(LocalizedEnvironmentFilter.java:69) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.EnvironmentFilter.doFilter(EnvironmentFilter.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.SessionFilter.doFilter(SessionFilter.java:55) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.redhat.rhn.frontend.servlets.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:97) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:432) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1591) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: redstone.xmlrpc.XmlRpcFault: <class 'cobbler.cexceptions.CX'>:'login failed (<myaccount>)' at redstone.xmlrpc.XmlRpcClient.handleResponse(XmlRpcClient.java:444) at redstone.xmlrpc.XmlRpcClient.endCall(XmlRpcClient.java:376) at redstone.xmlrpc.XmlRpcClient.invoke(XmlRpcClient.java:165) at com.redhat.rhn.manager.kickstart.cobbler.CobblerXMLRPCHelper.invokeMethod(CobblerXMLRPCHelper.java:69) at com.redhat.rhn.manager.kickstart.cobbler.CobblerLoginCommand.login(CobblerLoginCommand.java:51) ... 50 more It's not clear to me why trying to remove a system would be causing cobbler exceptions. Any ideas or suggestions? Thanks Paul-Andre Panon

1 0

Uyuni 2022.03 is released!
by Julio Gonzalez 04 Apr '22

04 Apr '22

We are happy to announce the immediate availability of Uyuni 2022.03 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.03, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Fixes for Salt security issues - New XML-RPC API version 26 - smdba: changed defaults for newer PostgreSQL versions - Monitoring: Grafana 8.3.5 - Salt SSH now uses the Salt Bundle - Some products are now becoming unsupported Please check the release notes for full details. For the Salt Security issues, you must update the Salt master on the Uyuni Server before updating any client. 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.03 As always, we hope you will enjoy Uyuni 2022.03 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

1 1

IMPORTANT: Broken salt communications between minions and master on 2022.02, after the last fixes for Salt CVEs
by Julio Gonzalez 01 Apr '22

01 Apr '22

Hello, If you suddenly see at your minions: 2022-03-28 13:19:41,880 [salt.crypt :743 ][ERROR ][15942] Sign-in attempt failed: {'publish_port': 4505, 'pub_key': '-----BEGIN PUBLIC KEY----- \n...\n-----END PUBLIC KEY-----\n''enc': 'pub','sig': ".."} 2022-03-28 13:19:41,885 [salt.minion :1056][ERROR ][15942] Error while bringing up minion for multi-master. Is master at salt-master-server.tf.local responding? That's a consecuence of the fixes for the last Salt CVEs. The official solution is updating to Uyuni 2022.03 If you want to stay on 2022.02, this is an unofficial, untested and unsupported solution: - Apply the updates for the Salt Master on the server - Resync all client tools - Update the salt minon at all salt clients Best regards. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

RE: Set up Uyuni with YaST ERROR
by Paul-Andre Panon 28 Mar '22

28 Mar '22

Hi Julio, I am getting the same error. This is with a new install of Uyuni 2022.02. It looks like the certificate is getting created in /root/ssl-build but the rpm package is not. I manually copied the certificate and key to the locations in /etc/pki/tls/ indicated by the apache2 config to be able to start the web service, but we need to build the cert rpm package for deployment to clients. We're actually going to go through the procedure to build a custom CA-signed cert so we will see whether that goes OK or if it breaks as well, but the default process for using a self-signed cert seems to be broken after the creation of the cert. The self signed cert also appears to have the OU and O order mixed up, although I expect that shouldn't be enough to break the cert configuration. Cheers, Paul-Andre Panon

1 1

Uyuni 2022.02 is released!
by Julio Gonzalez 18 Mar '22

18 Mar '22

We are happy to announce the immediate availability of Uyuni 2021.02 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.02, including the release notes, documentation, requirements and setup instructions. VERY IMPORTANT: Read the release notes! If you are updating from an Uyuni version older than 2021.06, a major upgrade procedure is required. This is the list of highlights for this release: * Reporting Database * Ubuntu errata installation * Monitoring: Prometheus 2.32.1 * Monitoring: Postgres exporter updated to version 0.10.0 for SUSE Linux Enterprise and openSUSE * SLES PAYG client support on cloud * openscap for Debian 11 (Tech Preview) Please check the release notes for full details, and in particular review the section about the Postgres exporter update and the Prometheus update, as it could require manual if you are using monitoring. 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.02 As always, we hope you will enjoy Uyuni 2022.02 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

5 7

Using Prometheus and Grafana on Centos
by Simon Avery 15 Mar '22

15 Mar '22

Has anyone managed to get the Grafana dashboards working on Centos or Rocky? I have tried several times over various versions and just given another hour to the task without any joy. Following the guide and applying the Salt formula always fails on the targets I've tried, with: ID: install_prometheus Function: pkg.installed Name: golang-github-prometheus-prometheus Result: false Comment: Error occurred installing package(s). Additional info follows: errors: - Running scope as unit: run-r4cd5eeb15cd8494685380c6107f1045b.scope Last metadata expiration check: 0:00:03 ago on Thu Mar 10 14:37:34 2022. No match for argument: golang-github-prometheus-prometheus Error: Unable to find a match: golang-github-prometheus-prometheus Started: 14:37:18.669658 Duration: 20980.625 SLS: prometheus Changed: {} And indeed - the package is not called that on EL. It is supplied in the Epel repos (although on Centos 7 that appears to be broken - it does install fine manually on Rocky 8) - but the package is called golang-github-prometheus - so always fails. Anyone know how to work around this? I don't have any Suse machines other than the one Uyuni runs on. Manually, I always seem to get into configuration problems with Prometheus. It's not software I'm familiar with and it does seem very fussy about syntax (something I've seen discussed at https://github.com/uyuni-project/uyuni/issues/2082 ) I have an existing Grafana server that I'd like to be able to use this with. Simon Avery Linux Systems Administrator: ATASS Sports Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH t: 01392 440 400 e: simon.avery(a)atass-sports.co.uk<mailto:simon.avery@atass-sports.co.uk> www.atass-sports.co.uk<https://gbr01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.atass-…> Follow us on Twitter: @atassSports<https://twitter.com/atassSports> NOTICE This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy

2 4