- ARCHIVED: Uyuni Development

Mailing lists (except "announce") are now archived, discussions happening now at GitHub discussions
by Julio Gonzalez 25 Apr '23

25 Apr '23

Hello. As announced last week, the following list are now archived: - devel(a)lists.uyuni-project.org - users(a)lists.uyuni-project.org - translation(a)lists.uyuni-project.org While we will keep the following one active: - announce(a)lists.uyuni-project.org All asynchronous discussions are now happening at https://github.com/uyuni-project/uyuni/discussions And as always, remember Gitter [1] is available as well for synchronous discussions. Happy hacking! https://www.uyuni-project.org/pages/contact.html#gitter -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Mailing lists (except "announce") to be archived on April 24th, moving to GitHub discussions
by Julio Gonzalez 20 Apr '23

20 Apr '23

Hello, As agreed by the community at https://github.com/uyuni-project/uyuni/discussions/6821, after two weeks collecting votes, we will be moving from mailing lists to GitHub Discussions (https://github.com/uyuni-project/uyuni/discussions) This means we will archive the following mailing lists: - devel(a)lists.uyuni-project.org - users(a)lists.uyuni-project.org - translation(a)lists.uyuni-project.org While we will keep the following one active: - announce(a)lists.uyuni-project.org Archival is going to be done on Monday morning (April 24th), and another announcement will follow to this list. We recommend avoid opening new threads on the mailing lists, and instead create discussions at GitHub, so the followups happen there, after the archival of the mailing lists. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

CI: Running Acceptance tests at PR: Beta Users wanted
by Jordi Massaguer Pla 20 Apr '23

20 Apr '23

Hi! Do you want to run the acceptance tests on your Pull Requests to ensure you did not introduce any regression? Do you want to do this with less than 30 minutes instead of the 8 hours it used to take? Sign it to be a beta user here: https://github.com/uyuni-project/uyuni/wiki/Running-Acceptance-Tests-at-PR#… Note we are not running the whole secondary testsuite. We are running 30% of them and increasing. Please help us as a beta user. For help you can reach me at https://www.uyuni-project.org/pages/contact.html#gitter Greetings jordi

1 0

POLL: GitHub discussions or mailing lists for Uyuni for async discussions?
by Julio Gonzalez 13 Apr '23

13 Apr '23

Hello, Since GitHub discussions were enabled in 2020, we have both systems. But that means everyone is duplicating the effort, as both places need to be checked to see if the question you want to ask is there, or if there was a reply. Therefore, we need to pick one system and close the other one. NOTE: We'd still keep the mailing list for announcements You can get more details and vote at: https://github.com/uyuni-project/uyuni/discussions/6821 The poll will be open for 2 weeks, until April 19th 17.00 CEST Remember to vote! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 2

Community Hours tomorrow, Friday 31st, at 16.00 CEST
by Julio Gonzalez 30 Mar '23

30 Mar '23

Hello, As every last Friday of each month, we'll be having tomorrow a session of the Uyuni Community Hours. The agenda (as of today) is: - Hack Week: OpenSCAP usability improvements - Hack Week: Code coverage of Uyuni triggered by our Cucumber Test suite - Visualising Salt events - Project Lotus - Syncing optional channel from UI (and not just from CLI) The link to join is: https://teams.microsoft.com/l/meetup-join/19%3Ameeting_ZjZlMWI0OTctNGMxZi00… Remember you can find all the information about the Community hours, included updated agenda and link for the meeting at https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours See you there! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

ERRATA for debian or ubuntu Client
by Benoit Barriere 24 Mar '23

24 Mar '23

Hello, I am experimenting uyuni (2023.03) and i would like to know if official documentation exist concerning importing ERRATAs into UYUNI. In errata i mean USN and DSA bulletins regding Ubuntu and Debian. I have read in a changelog current 2022 that UYUNI can import all ubuntu erratas from a json database file provided by Ubuntu but how to do that ? no documentation is provided. Concerning Ubuntu i am refreshing my experience on spacewalk 2.10 using old scripts to parse announcements from Ubuntu and import into UYUNI by api and that's work correctly. For Debian scripts don't work and the debian patching look like not be easy if no DSAs exist in UYUNI. So if someone can help on this topic i will appreciate. Kinds regards, Benoit Barriere

2 2

IMPORTANT: Security Patch for Uyuni Server 2023.03
by Julio Gonzalez 22 Mar '23

22 Mar '23

Hello! The SUSE Customer support team detected a security problem that caused the password used for bootstrapping or virtual host manager configuration to be captured in clear text in the rhn_web_api.log A patch for Uyuni 2023.03 is now available, and we recommend you apply it as soon as possible, without waiting for the next release (that obviously will include it as well. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2023.01 or earlier, update first to 2023.03 normally (make sure you read the release notes, as special steps maybe required if you are not on 2023.03 already), and then apply the patch as explained above. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

IMPORTANT: Patch for Uyuni Server 2023.03 and blank notification page for users with SCC accounts
by Julio Gonzalez 16 Mar '23

16 Mar '23

Hello! Some users reported that after the update to Uyuni 2023.03, the notification page was completely blank [1] [2] If you are affected, you will see notifications on the bell icon at the WebUI, and you will still get e-mail notifications. But if you go to the notifications page, it will render completely blank, with no content at all or errors. Although this should only affect Uyuni users with SCC credentials added to the Setup Wizard and with SCC subscriptions expiring, a previous bug [3] can cause this same problem even for some users without SCC subscriptions if they got such notifications but never removed them. A patch for Uyuni 2022.03 is now available, in case you are affected, so you do not need to wait for the next Uyuni release. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2023.01 or earlier, update first to 2023.03 normally (make sure you read the release notes, as special steps may be required if you are not on 2023.03 already), and then apply the patch as explained above. Happy hacking! [1] https://lists.opensuse.org/archives/list/users@lists.uyuni-project.org/mess… [2] https://github.com/uyuni-project/uyuni/issues/6729 [3] https://github.com/uyuni-project/uyuni/issues/6375 -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Kickstart profile creation fails (on Enterprise Linux 9)
by Stefan Bluhm 07 Mar '23

07 Mar '23

Hello, can anyone supply me an idea what to look for/at to solve the below issue? (keep in mind, that I am not using the Leap Java bundles/versions) Steps taken: 1. Go to https://<server>/rhn/kickstart/CreateProfileWizard.do 2. Follow the wizard to the end past the password screen 3. Click on Finish Expectation: New profile shows up and can be Uyuni-managed Reality: "Internal Server Error" shows up. On loading the profile screen, the profile is there but cannot be Uyuni-managed. /var/log/cobbler/cobbler.log does not seem to show anything releavant (errors). /var/log/rhn/web* did not get any new entries or have not been created after deletion and restart. /var/log/tomcat/catalina.2023-02-16.log 16-Feb-2023 09:31:33.473 SEVERE [http-nio-127.0.0.1-8080-exec-1] org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError Failed to call onError method of POJO end point for POJO of type [com.suse.manager.webui.websocket.Notification] java.lang.reflect.InvocationTargetException 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.tomcat.websocket.pojo.PojoEndpointBase.onError(PojoEndpointBase.java:134) at org.apache.tomcat.websocket.WsFrameBase.handleThrowableOnSend(WsFrameBase.java:579) at org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:418) at org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:129) at org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:515) at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:301) at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:133) at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:85) at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:183) at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:162) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:157) at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:60) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.NullPointerException at com.suse.manager.webui.websocket.Notification.onError(Notification.java:150) ... 24 more 16-Feb-2023 09:32:01.557 WARNING [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-10] org.apache.struts.action.RequestProcessor.processException Unhandled Exception thrown: class java.lang.reflect.InvocationTargetException /var/log/tomcat/localhost.2023-02-16.log 16-Feb-2023 09:32:01.578 SEVERE [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-10] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [action] in context with path [/rhn] threw exception [jav a.lang.reflect.InvocationTargetException] with root cause redstone.xmlrpc.XmlRpcFault: <class 'TypeError'>:cannot marshal None unless allow_none is enabled 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 org.cobbler.CobblerConnection.invokeMethod(CobblerConnection.java:146) at org.cobbler.CobblerConnection.invokeMethod(CobblerConnection.java:162) at org.cobbler.CobblerObject.refreshResolved(CobblerObject.java:360) at org.cobbler.CobblerObject.modify(CobblerObject.java:341) at org.cobbler.CobblerObject.modify(CobblerObject.java:321) at org.cobbler.Profile.setDistro(Profile.java:724) at org.cobbler.Profile.setDistro(Profile.java:715) at com.redhat.rhn.manager.kickstart.cobbler.CobblerProfileCommand.updateCobblerFields(CobblerProfileCommand.java:75) at com.redhat.rhn.manager.kickstart.cobbler.CobblerProfileCreateCommand.store(CobblerProfileCreateCommand.java:107) at com.redhat.rhn.manager.kickstart.KickstartWizardHelper.store(KickstartWizardHelper.java:187) at com.redhat.rhn.domain.kickstart.builder.KickstartBuilder.create(KickstartBuilder.java:585) at com.redhat.rhn.frontend.action.kickstart.CreateProfileWizardAction.runComplete(CreateProfileWizardAction.java:297) 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 com.redhat.rhn.frontend.struts.wizard.WizardStep.invoke(WizardStep.java:115) at com.redhat.rhn.frontend.struts.wizard.RhnWizardAction.dispatch(RhnWizardAction.java:104) at com.redhat.rhn.frontend.struts.wizard.RhnWizardAction.execute(RhnWizardAction.java:90) at com.redhat.rhn.frontend.action.kickstart.CreateProfileWizardAction.execute(CreateProfileWizardAction.java:104) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:237) at com.redhat.rhn.frontend.struts.RhnRequestProcessor.process(RhnRequestProcessor.java:104) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:681) at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.redhat.rhn.frontend.servlets.AuthFilter.doFilter(AuthFilter.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) 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:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter.doFilter(LocalizedEnvironmentFilter.java:71) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.redhat.rhn.frontend.servlets.EnvironmentFilter.doFilter(EnvironmentFilter.java:102) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.redhat.rhn.frontend.servlets.SessionFilter.doFilter(SessionFilter.java:59) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.redhat.rhn.frontend.servlets.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:360) at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:433) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:829) Thank you and best wishes, Stefan

2 3

Uyuni 2023.03 is released!
by Julio Gonzalez 02 Mar '23

02 Mar '23

VERY IMPORTANT: 2023.03 may require a special procedure if you are not upgrading from 2023.01 Make sure you read the release notes for all the versions between the one you are using now, and 2023.03! We are happy to announce the availability of Uyuni 2023.03. Most openSUSE mirrors should already have 2023.03, 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 2023.03, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - openSUSE Leap Micro 5.3 support as client - SUSE Linux Enterprise Server Micro product migration - New products enabled - Monitoring: Grafana update to 8.5.15 - Syncing optional channels from from the WebUI - Subscription warning notifications will now happen weekly - Documentation: New look and feel - Salt 3000 End of Life - Debian 9 End of Life - 'spacewalk-clone-by-date' has been deprecated 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 2023.03. As always, we hope you will enjoy this new Uyuni version 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

Community Hours today at 16.00 CET
by Julio Gonzalez 24 Feb '23

24 Feb '23

Hello, As every last Friday of each month, we'll be having a session of the Uyuni Community Hours. The agenda for today is: - Uyuni 2023.02/2023.03: What's new? (Julio) - Uyuni roadmap (Abid) - Hack Week: New Operating systems as clients for Uyuni (Raul and Julio) - Hack Week: Building the documentation on any OS and with no toolchain (Julio) - Hack Week: Improvements on the Uyuni Health Check tool (Pablo) - Hack Week: Deploying Uyuni Proxy container with fleet and elemental (Cedric) The link to join is: https://teams.microsoft.com/l/meetup-join/19%3Ameeting_ZjZlMWI0OTctNGMxZi00… See you there! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Susemanager package - Remove Python 2
by Stefan Bluhm 04 Feb '23

04 Feb '23

Hello, I am currently touching the susemanager.spec file for the susemanager package and noticed the if statements for Python 2 and 3. Can I remove the Python 2 references or are they still needed? Best wishes, Stefan

1 0

Uyuni 2023.01 is released!
by Julio Gonzalez 30 Jan '23

30 Jan '23

VERY IMPORTANT: 2023.01 will require a special procedure if you are not upgrading from 2022.12 Make sure you read the release notes for all the versions between the one you are using now, and 2023.01! We are happy to announce the availability of Uyuni 2023.01. Most openSUSE mirrors should already have 2023.01, 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 2023.01, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Release notes cleanup - SUSE Linux Enterprise Micro support as client - Content Lifecycle Management: Disabling modularity for AppStream repositories 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 2023.01. As always, we hope you will enjoy this new Uyuni version 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

EoL operating systems to be removed from systemsmanagement:Uyuni:Utils
by Julio Gonzalez 09 Jan '23

09 Jan '23

Hello! We keep a lot of packages at https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Utils that useful for development or release engineering. By March 31st, we'll be removing the following repositories from that project: CentOS_8 SLE_15 openSUSE_Leap_15.0 openSUSE_Leap_15.1 openSUSE_Leap_15.2 openSUSE_Leap_15.3 Debian_9.0* xUbuntu_16.04* xUbuntu_18.10* xUbuntu_19.04* Such OS are end of life (EoL), so if you are using them, please migrate to a supported version before March 31st. Removing such repositories will free resources for the Open Build Service, which is always crowded. This will not affect Uyuni itself, as such packages are not shipped with Uyuni. EXTRA: You will noticed some recent Debian/Ubuntu/Fedora versions were not added. If you need them, let us know, so we can enable the repositories, and please help us fixing the building problems, in case there are any. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2022.12 is released!
by Julio Gonzalez 20 Dec '22

20 Dec '22

VERY IMPORTANT: 2022.12 will require a special procedure if you are not upgrading from 2022.11 Make sure you read the release notes for all the versions between the one you are using now, and 2022.12! We are happy to announce the availability of Uyuni 2022.12. Most openSUSE mirrors should already have 2022.12, 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.12, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Indications for systems requiring reboot or with a scheduled reboot - Notification messages via email - Monitoring: Grafana update to 8.5.15 - Subscription warning notifications - Limit changelogs at repositories metadata to the last 20 entries - Drop legacy way to prevent disabling local repositories at bootstrap scripts 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.12. As always, we hope you will enjoy Uyuni 2022.12 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

Canceled: Uyuni Community Hours
by Julio Gonzalez 16 Dec '22

16 Dec '22

Dear Community: The December session of the Community hours will be skipped, as a lot of people is away because of the winter holidays. See you again in January, or at Gitter/Mailing lists. Happy hacking!

1 0

IMPORTANT: Security Patch for Uyuni Server 2022.11
by Julio Gonzalez 13 Dec '22

13 Dec '22

Hello! The SUSE security team detected a security problem that caused the proxy password to be present at the browser log, when using the Uyuni Server via WebUI. A patch for Uyuni 2022.11 is now available, and we recommend you apply it as soon as possible, without waiting for the next release (that obviously will include it as well. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2022.10 or earlier, update first to 2022.11 normally (make sure you read the release notes, as special steps required if you are not on 2022.10 already), and then apply the patch as explained above. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

IMPORTANT: Patch for Uyuni Server 2022.11 and Amazon Linux repository syncing
by Julio Gonzalez 02 Dec '22

02 Dec '22

Hello! A user has reported that after the update to Uyuni 2022.11, running spacewalk- repo-sync would fail with a permissions error, when trying to sync certain amazonlinux core channels. If you are affected, repository syncing will fail, and you will see errors similar to those reported at: https://github.com/uyuni-project/uyuni/issues/6244 This was due to a change in a script used by repo-sync, which checked if pages claiming to be mirrorlists were of the right media type. The check was overzealous and excluded some valid types of pages. A patch for Uyuni 2022.11 is now available, in case you are affected, so you do not need to wait for the next Uyuni release. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2022.10 or earlier, update first to 2022.11 normally (make sure you read the release notes, as special steps required if you are not on 2022.10 already), and then apply the patch as explained above. Thanks to eins for the report and the help debugging the issue. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

IMPORTANT: Patch for Uyuni Server 2022.11
by Julio Gonzalez 25 Nov '22

25 Nov '22

Hello! Several users at Gitter and GitHub have reported that after the update to Uyuni 2022.11, they see a notification whith an error message after a reposync for any channel is complete. The error will contain a python stacktrace as described at https://github.com/uyuni-project/uyuni/issues/6193 Uyuni 2022.11, includes a refactor for the System list page to use a dedicated cache table to improve performance. Because of this refactor, each time a repository is synchronized, we need to refresh the information for the minions using such repository. The query that processes such refresh had a bug, and was referring a non- existing reference. A patch for Uyuni 2022.11 is now available, in case you are affected, so you do not need to wait for the next Uyuni release. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html If you are still on 2022.10 or earlier, update first to 2022.11 normally (make sure you read the release notes, as special steps required if you are not on 2022.10 already), and then apply the patch as explained above. Thanks to all users that reported the issues, and helped with the debugging. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

IMPORTANT: Refresh of the Uyuni 2022.11 release notes
by Julio Gonzalez 23 Nov '22

23 Nov '22

Hello! Some users reported two issues: # System list showing empty after the update See: https://www.uyuni-project.org/doc/2022.11/release-notes-uyuni-server.html#_… # Rocky Linux 9 onboarding fails to complete See: https://www.uyuni-project.org/doc/2022.11/release-notes-uyuni-server.html#_… As you can see, we refreshed the release notes at the website. If you want to have them refreshed at your Uyuni Server, we also released the refreshed release notes as a Patch, but keep in mind this is not strictly needed. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html Thanks to all users that reported the issues, and helped with the debugging. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2022.11 is released!
by Julio Gonzalez 21 Nov '22

21 Nov '22

VERY IMPORTANT: 2022.11 will require a special procedure if you are not upgrading from 2022.10 Make sure you read the release notes for all the versions between the one you are using now, and 2022.11! We are happy to announce the availability of Uyuni 2022.11. Most openSUSE mirrors should already have 2022.11, 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.11, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Instructions to disable custom channel automatic synchronization - Allow more tools for network management for the Uyuni Server - Monitoring: Grafana update to 8.5.13 - Monitoring: Fix TLS configuration and enable client certificate authentication for Blackbox exporter - Traditional stack being removed 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.11 As always, we hope you will enjoy Uyuni 2022.11 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

IMPORTANT: Patch for Uyuni Server 2022.10
by Julio Gonzalez 14 Nov '22

14 Nov '22

Hello! ################################################# WARNING: Instead of running `zypper up` as provided by the instructions at the website, we strongly recommend using `zypper up|tee /tmp/update.log` or similar, so you can find errors during the migration in the unlikely event they happen ################################################# Several users at Gitter and GitHub have reported that after the update to Uyuni 2022.10, and after applying the patch from last week, Cobbler had problems to start because templates files were not found, so some features were broken, such as: - Onboarding new clients - Removing existing clients - Autoinstallation In such cases you can see errors in Cobbler like: cobbler.cexceptions.CX: 'serializer: error loading collection profile: Invalid automatic installation template file location /var/lib/cobbler/templates/ xxxxxxxxxxxx.cfg, file not found This problem was caused because the "autoinstall" attribute for the Cobbler collections was wrongly migrated at the time of running the migration from the old Cobbler collections from version 2 to version 3, making Cobbler not able to find the "templates" files for the profiles anymore. Any subdirectory was removed from the "autoinstall" attribute. For "Autoinstallation" profiles generated using Uyuni, the "autoinstall" files are generated and placed by Uyuni at "upload/" and "wizard/" subdirectories of `/var/lib/cobbler/templates/`. These Cobbler collections and templates files (for Uyuni created profiles) are recreated by Uyuni in case they are missing, on every spacewalk-services restart. With this new upgrade, we have fixed the migration of the "autoinstall" attribute from Cobbler collections, and make the migration to run again in order to fix any possible inconsistency created by the execution of the wrong migration from the previous patch, so Cobbler will be now able to find the "autoinstall" templates and finish the startup. The migration will run automatically during the upgrade, if there is any unexpected issue during the migration you should see some errors when zypper is updating "cobbler" or "spacewalk-setup" packages. In the unlikely event there are still some conflicts for the `.cfg` files, you will get instructions provided by the upgrade, to fix the issue. A patch for Uyuni 2022.10 is now available, in case you are affected, 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 (please be aware of the WARNING at the beginning of this email!) Thanks to all users that reported the issues, and helped with the debugging. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

IMPORTANT: Security patches and feature patches for Uyuni Server 2022.10
by Julio Gonzalez 04 Nov '22

04 Nov '22

Hello! ### Cobbler migration Some users have reported that after the Update to Uyuni 2022.10, there are still some problems related to Cobbler, where collections are not migrated, so the cobbler service fails to start at the Uyuni Server. In such situations some features can be broken, such as: - Onboarding new clients - Removing existing clients - XML-RPC via HTTP - spacecmd - spacewalk-common-channels This is not happening for most users, but we are now releasing a patch to address it, and migrate any collections provided by any past cobbler version. ### File descriptors leakage Some users reported that, after updating to Uyuni 2022.10, and after some days, the Server stopped working, and they saw a steady increase of "open files" or "allocated file descriptors". This was caused after the migration to log4j2. Every time a taskomatic job object gets created, it initializes its own logger programmatically to write its logs into a file. The lifecycle of a job object is relatively short, but the log4j2 runtime doesn't know it. When it gets permissions to write into a file, there's nothing to release it after the job is over. Moreover the log4j2 keeps track of loggers based on the class names. It effectively means we mutate the same logger object in memory over and over again with every new taskomatic job. The fix adds functionality to re-initialize the logger when a new job comes around, dropping any file handler it has. ### Security fixes During a SUSE Manager and Uyuni security audit, the SUSE security team reported three vulnerabilities at the spacewalk-java source package (which provides spacewalk-java-* or spacewalk-taskomatic packages): * CVE-2022-31255: Fix directory path traversal vulnerability * CVE-2022-43754: Fix reflected cross site scripting vulnerability * CVE-2022-43753: Fix arbitrary file disclosure vulnerability You can find more details at: https://www.suse.com/security/cve/CVE-2022-31255.html https://www.suse.com/security/cve/CVE-2022-43754.html https://www.suse.com/security/cve/CVE-2022-43753.html A patch for Uyuni 2022.10 to fix all the issues was just published, and because of the security issues, it is strongly recommended you update your server, even if you are not affected by the cobbler migration issues or the file descriptors leakage. You can apply the patch at the Uyuni Server by following the instructions at: https://www.uyuni-project.org/pages/patches.html Thanks to all users that reported the issues, and helped with the debugging. Happy hacking!

1 0

Canceled: Uyuni Community Hours
by jgonzalez＠suse.com 24 Oct '22

24 Oct '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: Patch for Uyuni Server 2022.10
by Julio Gonzalez 24 Oct '22

24 Oct '22

Hello! Several users at Gitter have reported that after the Update to Uyuni 2022.10, and after applying the patch from last week, that the cobbler package fails to update, or that the cobbler service is not starting at the Uyuni Server. In such situations some features can be broken, such as: - Onboarding new clients - Removing existing clients - XML-RPC via HTTP - spacecmd - spacewalk-common-channels The problem was causes because of bugs at migration scripts for cobbler itself. Such bugs are only happening for long time Uyuni users where the cobbler configuration is old enough, so most users should not notice this problem. If you are affected, you will see the following error while installing the cobbler package: > schema.SchemaError: Key 'proxy_url_ext' error: > None should be instance of 'str' Or the following error at the logs, when starting cobbler: > cobblerd[32057]: schema.SchemaError: Key 'allow_duplicate_hostnames' error: > cobblerd[32057]: 0 should be instance of 'bool' The fix is at the SR: https://build.opensuse.org/package/rdiff/systemsmanagement:Uyuni:Master/cob… (an OBS account is required to see the diff) 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