- ARCHIVED: Uyuni Development

IMPORTANT: Patch for Uyuni Server 2022.10
by Julio Gonzalez 20 Oct '22

20 Oct '22

Hello! Several users at GitHub, mailing lists and Gitter have reported that after the Update to Uyuni 2022.10, cobbler is not starting at the Uyuni Server, therefore affecting some features, such as: - Onboarding new clients - Removing existing clients - XML-RPC via HTTP - spacecmd - spacewalk-common-channels The following bug reports are related to this problem: - https://github.com/uyuni-project/uyuni/issues/6037 - https://github.com/uyuni-project/uyuni/issues/6041 - https://github.com/uyuni-project/uyuni/issues/6045 The problem was caused for a bug at the script for the migration of the settings and collections to Cobbler 3.3.3 The fix is at the PR https://github.com/uyuni-project/uyuni/pull/6050 A patch for Uyuni 2022.10 to fix both problems was just published, in case you are affected, and so you do not need to wait for Uyuni 2022.11 (this version will also include this fix) You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html Thank to all users that reported the issue, and helped with the debugging Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Java rhn webapp not starting on Enterprise Linux 9
by Stefan Bluhm 19 Oct '22

19 Oct '22

Hello all, I am having an issue on starting the rhn Webapp on Tomcat with Enterprise Linux 9. Can you give me some pointers on what to look at? I have partially bodged together my own Java jars... From what I can tell, this seems to be the only log entry (unless I am overlooking something): /var/log/tomcat/localhost.2022-10-17.log 17-Oct-2022 21:07:12.279 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.redhat.rhn.webapp.RhnServletListener] java.lang.NullPointerException at com.redhat.rhn.common.hibernate.AbstractConnectionManager.getSession(AbstractConnectionManager.java:258) at com.redhat.rhn.common.hibernate.HibernateFactory.getSession(HibernateFactory.java:352) at com.redhat.rhn.common.hibernate.HibernateFactory.listObjectsByNamedQuery(HibernateFactory.java:275) at com.redhat.rhn.common.hibernate.HibernateFactory.listObjectsByNamedQuery(HibernateFactory.java:220) at com.redhat.rhn.domain.reactor.SaltEventFactory.countSaltEvents(SaltEventFactory.java:55) at com.suse.manager.reactor.PGEventStream.<init>(PGEventStream.java:105) at com.suse.manager.webui.services.impl.SaltService.createEventStream(SaltService.java:579) at com.suse.manager.webui.services.impl.SaltService.createOrGetEventStream(SaltService.java:533) at com.suse.manager.webui.services.impl.SaltService.getEventStream(SaltService.java:587) at com.suse.manager.reactor.SaltReactor.connectToEventStream(SaltReactor.java:190) at com.suse.manager.reactor.SaltReactor.start(SaltReactor.java:161) at com.redhat.rhn.webapp.RhnServletListener.contextInitialized(RhnServletListener.java:130) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4768) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5230) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:690) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:583) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:473) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1618) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423) at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:946) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:265) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Catalina.start(Catalina.java:772) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476) 17-Oct-2022 21:07:12.417 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStop Exception sending context destroyed event to listener instance of class [com.redhat.rhn.webapp.RhnServletListener] java.lang.NullPointerException at com.redhat.rhn.common.hibernate.AbstractConnectionManager.close(AbstractConnectionManager.java:121) at com.redhat.rhn.common.hibernate.HibernateFactory.closeSessionFactory(HibernateFactory.java:92) at com.redhat.rhn.webapp.RhnServletListener.stopHibernate(RhnServletListener.java:107) at com.redhat.rhn.webapp.RhnServletListener.contextDestroyed(RhnServletListener.java:164) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4816) at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5477) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:257) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:187) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:690) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:583) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:473) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1618) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423) at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:946) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:265) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Catalina.start(Catalina.java:772) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476) Thank you and best wishes, Stefan

1 0

Uyuni 2022.10 is released!
by Julio Gonzalez 14 Oct '22

14 Oct '22

VERY IMPORTANT: 2022.10 requires special procedures for the upgrade from any previous version! Make sure you read the release notes for all the versions between the one you are using now, and 2022.10! We are happy to announce the availability of Uyuni 2022.10. Most openSUSE mirrors should already have 2022.10, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.10, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Special instructions for the update, make sure you read them! - RHEL/Oracle Linux/AlmaLinux/Rocky Linux 9 as clients - Monitoring for Ubuntu 22.04 - pip support for the Salt Bundle - Apache exporter updated to version 0.11.0 for SUSE Linux Enterprise and openSUSE - Cobbler updated to version 3.3.3 Remember that Uyuni follows 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.10 As always, we hope you will enjoy Uyuni 2022.10 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 0

Code scanning using SonarCloud
by Cedric Bosdonnat 27 Sep '22

27 Sep '22

Hi all, I am pleased to announce you that I finally managed to setup SonarCloud to analyze the Uyuni code. https://sonarcloud.io/project/pull_requests_list?id=uyuni-project_uyuni You can just login there with your github account so that it associates the founds issues with your user. Concretely, there are two kinds of scans: * Periodic scans on the master branch * Scans on each PR containing Java code The scans are run on SUSE infrastructure and the results are published to SonarCloud. You can help in two ways: * Get the sonarcloud report is green on your Java PRs * Fix issues you can find in the sonarcloud UI I hope you will enjoy that new tool! -- Cédric

1 0

Canceled: Uyuni Community Hours
by jgonzalez＠suse.com 26 Aug '22

26 Aug '22

The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.

1 0

IMPORTANT: All packages at the Git repository are now bumped to be 4.4.0
by Julio Gonzalez 10 Aug '22

10 Aug '22

Hello, As you can see at https://github.com/uyuni-project/uyuni/pull/5759, I bumped all the packages to be 4.4.0 For any existing PRs you already have against master: - Check if you have schema migration scripts. If so, move them to the relevant 4.4.0-to-4.4.1 folder -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2022.08 is released!
by Julio Gonzalez 10 Aug '22

10 Aug '22

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also needs to be updated. Make sure you read the release notes before updating! We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy and Retail Branch Server 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.08 As always, we hope you will enjoy Uyuni 2022.08 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 0

A fix for using HTTP proxies for repository synced is now released
by Julio Gonzalez 21 Jul '22

21 Jul '22

The fix requires two things: - Uyuni 2022.06 - The latest python3-urlgrabber from openSUSE Leap 15.4 The issue is being tracked at https://github.com/uyuni-project/uyuni/issues/4850 Special thanks to Dan Holstad, hbrown-uiowa, phibid and SpeedBlack for the report, and to Dominik Wombacher and Pablo Suárez for the fix. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

WIP: Uyuni Ansible Collection
by Christian Stankowic 12 Jul '22

12 Jul '22

Hi Uyuni team, after I started working on an Ansible role for installing and configuring Uyuni (https://github.com/stdevel/ansible-uyuni) back in 2020, I recently started working on an Ansible Collection. Using this collection, you can currently install patches and package upgrades. For the future, it is planned to implement other functionality such as Content Lifecycle Mangement maintenance and managing Activation Keys. The collection is still in an early stage - I tested the current functionality successfully against the last two Uyuni versions. Development is completely open-source: https://github.com/stdevel/ansible-collection-uyuni/ I documented some TODOs and ideas as issues - feel free to let me know what you think! I can demonstrate the collection in one of the next Uyuni Community Hours, if you like! Best regards, Christian.

1 0

Patch for Uyuni 2022.06
by Julio Gonzalez 06 Jul '22

06 Jul '22

Hello! Several users syncing openSUSE Leap 15.3/15.4 and/or the SUSE PackageHub reported that they are getting the following error running reposync from CLI, or at the WebUI notifications area: 2022/07/05 09:22:01 +02:00 Importing packages to DB: 2022/07/05 09:22:02 +02:00 'rpm.hdr' object has no attribute 'get' Please note that this bug does **not** prevent syncing other packages, it just means that the package `kicad-packages3D` version `5.1.8-bp154.1.18` failed to sync due to the bug. So it wont be available for Uyuniu clients, as it won't be synced at the server. Other than that the reposync will work just as usual. If automated syncing is for the affected channels is enabled, then you will also get notifications at the UI (the "bell" icon). A patch for Uyuni 2022.06 to fix both problems was just published, in case you do not want to wait for Uyuni 2022.07 (it will be part of that release as well). You can apply the patch by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are using Uyuni 2022.05 or older: make sure you update to 2022.06, and remember 2022.06 changes the base OS to openSUSE Leap 15.4, so you need to follow a special procedure (check the release notes). Thank to all users that reported the issue, and specially to Jonathan Müller (LordofAgents) for providing the information about the affected package. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Re: Uyuni 2022.06 is released!
by Julio Gonzalez 27 Jun '22

27 Jun '22

On lunes, 27 de junio de 2022 17:37:49 (CEST) Michele Bussolotto wrote: > > "In the Uyuni Server Web UI, navigate to proxy system's details page, > > click > > the Reactivation subtab. Click Generate New Key to generate a reactivation > > key." > > > > Is this really necessary ? I understand that we don't need to re-register > > the proxy. Just selecting the 15.4 repos and executing on the proxy > > 'zypper > > dup --allow-vendor-change' is enough, correct ? > > Correct, reactivation is no longer required. Thanks for noticing! @Philippe, can you maybe prepare a PR for the doc? It's quite easy, actually, the file is at https://github.com/uyuni-project/uyuni-docs/blob/master/modules/installatio… > ________________________________________ > From: Julio Gonzalez > Sent: Monday, June 27, 2022 5:27 PM > To: General discussion related to the openSUSE Uyuni project; > announce(a)lists.uyuni-project.org; devel(a)lists.uyuni-project.org; Bidault, > Philippe; Michele Bussolotto Subject: Re: Uyuni 2022.06 is released! > > > I can't tell for sure. > > @Michele? > > If it's not needed, then we should remove it from the doc. > > On lunes, 27 de junio de 2022 16:13:08 (CEST) Bidault, Philippe wrote: > > Hi Julio, > > > > Thanks for this ! Uyuni server upgraded, so far so good. > > > > However, I am still confused with the Proxy upgrade procedure > > (https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrad > > e > > /proxy-uyuni.html): > > > > "In the Uyuni Server Web UI, navigate to proxy system's details page, > > click > > the Reactivation subtab. Click Generate New Key to generate a reactivation > > key." > > > > Is this really necessary ? I understand that we don't need to re-register > > the proxy. Just selecting the 15.4 repos and executing on the proxy > > 'zypper > > dup --allow-vendor-change' is enough, correct ? > > > > Regards, > > Philippe. > > > > > > > > Philippe Bidault | Unix Engineer | Getronics > > > > M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com > > > > > > > > > > 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: www.getronics.com/legal and further details of how we > > treat your personal data can be found in our privacy policy > > <www.getronics.com/policy-pages/corporate-policy-legal-disclaimer> > > -----Original Message----- > > From: Julio Gonzalez via Uyuni Users <users(a)lists.uyuni-project.org> > > Sent: 27 June 2022 09:59 > > To: announce(a)lists.uyuni-project.org; users(a)lists.uyuni-project.org; > > devel(a)lists.uyuni-project.org Cc: Julio Gonzalez <jgonzalez(a)suse.com> > > Subject: Uyuni 2022.06 is released! > > > > 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. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Re: Uyuni 2022.06 is released!
by Julio Gonzalez 27 Jun '22

27 Jun '22

I can't tell for sure. @Michele? If it's not needed, then we should remove it from the doc. On lunes, 27 de junio de 2022 16:13:08 (CEST) Bidault, Philippe wrote: > Hi Julio, > > Thanks for this ! Uyuni server upgraded, so far so good. > > However, I am still confused with the Proxy upgrade procedure > (https://www.uyuni-project.org/uyuni-docs/en/uyuni/installation-and-upgrade > /proxy-uyuni.html): > > "In the Uyuni Server Web UI, navigate to proxy system's details page, click > the Reactivation subtab. Click Generate New Key to generate a reactivation > key." > > Is this really necessary ? I understand that we don't need to re-register > the proxy. Just selecting the 15.4 repos and executing on the proxy 'zypper > dup --allow-vendor-change' is enough, correct ? > > Regards, > Philippe. > > > > Philippe Bidault | Unix Engineer | Getronics > > M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com > > > > > 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: www.getronics.com/legal and further details of how we > treat your personal data can be found in our privacy policy > <www.getronics.com/policy-pages/corporate-policy-legal-disclaimer> > -----Original Message----- > From: Julio Gonzalez via Uyuni Users <users(a)lists.uyuni-project.org> > Sent: 27 June 2022 09:59 > To: announce(a)lists.uyuni-project.org; users(a)lists.uyuni-project.org; > devel(a)lists.uyuni-project.org Cc: Julio Gonzalez <jgonzalez(a)suse.com> > Subject: Uyuni 2022.06 is released! > > 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. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2022.06 is released!
by Julio Gonzalez 27 Jun '22

27 Jun '22

VERY IMPORTANT: Uyuni 2022.06 switches the base OS for the Server and the Proxy to openSUSE Leap 15.4. Make sure you read the release notes before updating! We are happy to announce the immediate availability of Uyuni 2022.06. At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.06, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Upgrade notes (read them carefully!) - Base system upgrade to openSUSE Leap 15.4 - PostgreSQL 14 - Salt 3004 - New products enabled 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.06 As always, we hope you will enjoy Uyuni 2022.06 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 0

Uyuni at the SUSE Hack Week #21
by Julio Gonzalez 22 Jun '22

22 Jun '22

Hi everyone, As every year, SUSE is celebrating its Hack Week, this time between June 27th and July 1st. Quoting the official definition: > Hack Week is the time SUSE employees and openSUSE community members experiment, innovate & learn interruption-free for a whole week! Across teams or alone, but always without limits. > > A SUSE tradition since 2007, Hack Week has brought together hundreds of hackers around the globe to collaborate on open source. > > SUSE Hack Week 21 theme is "Hacking for Humanity". All members of SUSE staff, community, partners and customers, with and without coding skills, are welcome to contribute to open source and any other kinds of projects. As last years, Uyuni is participating, so far with two projects that you can check at https://hackweek.opensuse.org/21/topics/uyuni Remember we have a "hackweek" channel at Gitter in case you want to participate in one of the existing projects, or if you want to create a new one. Also remember: you do not have to be a developer to help! You can help with documentation, translations, testing, bug reporting, web or graphic design, packaging, and a lot more. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Move/restore packages in OBS for EL
by Stefan Bluhm 30 May '22

30 May '22

Hello Julio, can you please restore antlr3-runtime to systemsmanagement:Uyuni:Master:Other:EL and copy the kit file to the EL Kit project? javassist-kit = de04b98f697133f5adc52913332122c9ba9dd3a9 antlr3-runtime-kit (I believe there was a kit file?) Thank you and best wishes, Stefan

3 6

python3-salt-3004 requires lower python3-zmq version
by Stefan Bluhm 25 May '22

25 May '22

Hello, As of python3-salt-3004 the package gets generated with the automatic requirement of (python3.9dist(pyzmq) < 22 with python3.9dist(pyzmq) > 19.0.2) This requirement hasn't been there for the python3-salt-3002 version and hasn't been specifically set in the SPEC file. Where would I look for identifying the issue? I guess this would be at https://github.com/saltstack/salt ? Enterprise Linux 9 ships with python3-zmq-22.3.0 Thanks, Stefan

1 0

AlmaLinux8 - Enable Module
by Stefan Bluhm 24 May '22

24 May '22

Hello, can you please add the following to the project config of https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master/prjconf https://build.opensuse.org/projects/systemsmanagement:Uyuni:Master:Other:EL… ExpandFlags: module:log4j-2 This enables the log4j v2 module. Thank you and best wishes, Stefan

2 1

Uyuni 2022.05 is released!
by Julio Gonzalez 10 May '22

10 May '22

IMPORTANT NOTE: The release is done, but it seems OpenBuildService is a bit overloaded now, so we recommend waiting at least a few hours before applying the update, to give more time for the mirrors to sync We are happy to announce the immediate availability of Uyuni 2022.05 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.05, including the release notes, documentation, requirements and setup instructions. VERY IMPORTANT: Always 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 documentation * spacewalk-report now uses data from the reporting database * Adding systems with failed actions to System Set Manager * Technology Preview: JSON over HTTP API 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.05 As always, we hope you will enjoy Uyuni 2022.05 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 0

Overview Coverage XMLRPC methods in spacecmd
by Dominik Wombacher 08 May '22

08 May '22

Hi, I was interested to see how many XMLRPC methods are available in spacecmd, without using the generic api function. Results based on the Uyuni Master branch as of today: Total: 721 Available: 336 Missing: 385 I wrote a quick & dirty bash script for the comparison, so it might not 100% accurate neither elegant, but gives a good indicator. When it comes to Automation, for example Ansible, I like using spacecmd under the hood and build some wrapper around. That leaves the heavy lifting and error handling with spacecmd, without re-inventing the wheel by creating new python modules that mostly contain the same code as spacecmd already does. Therefore I plan to implement some of the missing methods within the next time, for my needs most interesting will probably be: - ansible - actionchain - image* - recurringaction - saltkey - system (some of them like changeProxy or getConnectionPath) - user.external Just wanted to share that with you, the Bash Script I wrote and the results as csv file are also attached if someone is interested and want to take a look. Cheers Dominik -- The Wombelix Post https://dominik.wombacher.cc

2 1

Uyuni 2022.04 is released!
by Julio Gonzalez 29 Apr '22

29 Apr '22

IMPORTANT NOTE: The release is done, but it seems OpenBuildService is a bit overloaded now, so we recommend waiting at least a few hours before applying the update, to give more time for the mirrors to sync We are happy to announce the immediate availability of Uyuni 2022.04 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.04, including the release notes, documentation, requirements and setup instructions. VERY IMPORTANT: Always 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: * Salt SSH now uses the Salt Bundle * Technology Preview: Containerized Uyuni Proxy and Retail Branch Server * Reporting Database improvements * Improved image management * HSTS Enabled 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.04 As always, we hope you will enjoy Uyuni 2022.04 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 0

Uyuni 2022.03 new setups or updates, broken after April 20th 07:03UTC
by Julio Gonzalez 27 Apr '22

27 Apr '22

Hello, For those of you that installed Uyuni 2022.03 or updated from a previous version after pril 20th 07:03UTC, you will notice that the WebUI does not start and you see a HTTP error 404. Anyway that installed or updated before that date and time should not be affected by this This problem was caused by a netty update at openSUSE Leap 15.3. The bug report for Uyuni is available at: https://github.com/uyuni-project/uyuni/issues/5278 The explanation of why this happened is available at: https://github.com/uyuni-project/uyuni/issues/5278#issuecomment-1110868000 The remediation: - For Uyuni 2022.04 (release pending), this is alredy fixed by PR we merged this morning - For Uyuni 2022.03 you can apply a workaround: https://github.com/uyuni-project/uyuni/issues/5278#issuecomment-1110861789 -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

JUnit5 in master
by Cedric Bosdonnat 07 Apr '22

07 Apr '22

Hi all, I just merged the migration from JUnit3 to JUnit5 to master. For you this means: * You can use all the goodness of JUnit5 features, but do not enable parallel execution without carefull testing * Any new JUnit3 test you write will NOT be executed by the CI What makes a JUnit5 test? * Every test method needs to be annotated with org.junit.jupiter.api.Test * Every setup and teardown need to be annotated too * TestCase is no longer a base class for test classes * You need to statically import assertions from org.junit.jupiter.api.Assertions Checkout the help page for more details on JUnit5: https://junit.org/junit5/docs/current/user-guide/#writing-tests -- Cedric

1 0

Velocity 2 upgrade
by Cedric Bosdonnat 05 Apr '22

05 Apr '22

Hi Stefan, As agreed I merged the velocity2 upgrade. You can now add your changes to get it building on Alma Linux 8 -- Cedric

2 1

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