September 2021 - Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Fresh Install uyuni 2020.05 Error generating bootstrap repo
by Thomas Weis 24 Aug '22

24 Aug '22

Hello everyone we are configuring a fresh installation of Uyuni 2020.05 After a successful reposync of SUSE Linux Enterprise Server 15 SP1 x86_64 we get an error message: Type: Creating Bootstrap Repository failed Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 show details said: ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' not found ERROR: package 'python3-rhnlib' not found ERROR: package 'spacewalk-check' not found ERROR: package 'spacewalk-client-setup' not found ERROR: package 'spacewalk-client-tools' not found ERROR: package 'python3-spacewalk-check' not found ERROR: package 'python3-spacewalk-client-setup' not found ERROR: package 'python3-spacewalk-client-tools' not found ERROR: package 'python3-uyuni-common-libs' not found ERROR: none of 'mgr-daemon', 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found ERROR: package 'python3-suseRegisterInfo' not found ERROR: package 'zypp-plugin-spacewalk' not found ERROR: package 'python3-zypp-plugin-spacewalk' not found The installation was error-free, we proceeded exactly according to the documentation. What is our mistake? thanks for suggestions Regards Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

Need help with repository GPG settings.
by Allen Beddingfield 05 Oct '21

05 Oct '21

I have configured a repository and channel for Zabbix 5.4. It syncs and works as expected. For SUSE systems, I have unchecked "Enable GPG Check", and it works fine. Now, I have setup a repository for this for CentOS 7, but it gives errors similar to the following, when trying to install a package: "Public key for zabbix-agent2-5.4.5-1.el7.x86_64.rpm is not installed". It seems that just unchecking GPG check doesn't work with yum as it does with zypper. In the GPG section, for "GPG Key URL", I have put " http://repo.zabbix.com/RPM-GPG-KEY-ZABBIX-A14FE591" I'm not sure what to put for "GPG Key ID" or "GPG Key Fingerprint". The key in the URL is correct, because I can manually install that one on the client and have it work. How do I get this to work when the channel is associated with a CentOS system (as it does on SLES), without having to manually import that key on the system? Thanks. Allen B. -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu

1 1

Upgrade 2021.09 - Wrong vendor on packages?
by Simon Avery 05 Oct '21

05 Oct '21

Hi Thanks to all involved in the latest version - good to see it keep growing in strength! I did the upgrade from 2021.08 this morning, following the usual MINOR procedure. All seemed to have go well and Uyuni came back after rebooting and functioned normally. However - a question following the update and reboot - some updates and flagged as below. I'm guessing it is safe to override the vendor and install the new packages? Thanks ata-oxy-uyuni01:/home/simon # zypper up Loading repository data... Reading installed packages... The following 6 package updates will NOT be installed: mgr-osa-dispatcher python3-mgr-osa-common python3-mgr-osa-dispatcher python3-rhnlib python3-suseRegisterInfo suseRegisterInfo Nothing to do. ata-oxy-uyuni01:/home/simon # zypper up mgr-osa-dispatcher Loading repository data... Reading installed packages... There is an update candidate for 'mgr-osa-dispatcher' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install mgr-osa-dispatcher-4.3.1-1.2.uyuni1.noarch' to install this candidate. Resolving package dependencies... Nothing to do. simon@ata-oxy-uyuni01:~> zypper repos Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh --+-----------------------------+---------------------------------------------------------------------------------------------+---------+-----------+-------- 1 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No | ---- | ---- 2 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes 3 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes 4 | repo-oss | Main Repository | Yes | (r ) Yes | Yes 5 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ---- 6 | repo-sle-update | Update repository wiht updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes 7 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes 8 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes 9 | uyuni-server-stable | Uyuni Server Stable | Yes | (r ) Yes | Yes Simon Avery Linux Systems Administrator

3 5

Error when using "Product Migration" on openSuSE Clients
by Martin Willisegger 30 Sep '21

30 Sep '21

Hello list I get a system error every time I click on the "System Migration" menu item in uyuni with an openSuSE 15.3 client. This is not particularly bad, because a system migration is not offered with openSuSE. Nevertheless, this should not immediately cause an error. After that I get the following uyuni WEB TRACEBACK system mail: The following exception occurred while executing this request: GET /rhn/systems/details/SPMigration.do Date:9/30/21 5:22:26 PM CEST Headers: host: uyuni.wizonet user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0 accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8 accept-language: de,en-US;q=0.7,en;q=0.3 accept-encoding: gzip, deflate, br connection: keep-alive referer:https://uyuni.wizonet/rhn/systems/details/packages/Packages.do?date_hour=17&date_year=2021&schedule_type=date&date_month=8&date_day=30&date_minute=21&sid=1000010001 cookie: DWRSESSIONID=V56dyvHj2F9FrG4OVCcUm2VtqSe4uWziTMn; JSESSIONID=03FEFA72F1D29CC4B0C583AEDE4BE345; pxt-session-cookie=525659xd418885dfa66c3fa7dfc0579fc041f50ca7ec8ac2990cb8386ca1cd3553757df Upgrade-Insecure-Requests: 1 Sec-Fetch-Dest: document Sec-Fetch-Mode: navigate Sec-Fetch-Site: same-origin Sec-Fetch-User: ?1 Request: Local Name = uyuni.wizonet Server Name = uyuni.wizonet Requested Session Id came from Cookie Requested Session Valid = true Session = org.apache.catalina.session.StandardSessionFacade@6e0a108f[session=StandardSession[03FEFA72F1D29CC4B0C583AEDE4BE345]] Protocol = https Request Locale = en_US Request Character Encoding = UTF-8 Attribute Names = rhnActiveLang, org.apache.struts.action.MESSAGE, org.apache.struts.action.mapping.instance, targetProductSelectedEmpty, org.apache.tomcat.util.net.secure_protocol_version, requestedUri, isSUSEMinion, session, zyppPluginInstalled, isSaltUpToDate, javax.servlet.request.key_size, org.apache.struts.action.MODULE, isMinion, productMigrationForm, updateStackUpdateNeeded, javax.servlet.request.cipher_suite, javax.servlet.request.ssl_session_id, __sitemesh__filterapplied, upgradeSupported, system, javax.servlet.jsp.jstl.fmt.timeZone.request, javax.servlet.error.exception, User Information: User admin (id 1, org_id 1) Exception: javax.servlet.ServletException: java.lang.NullPointerException at org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433) 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.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) 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: java.lang.NullPointerException at com.redhat.rhn.domain.product.SUSEProductSet.toString(SUSEProductSet.java:256) at com.redhat.rhn.frontend.action.systems.SPMigrationAction.lambda$execute$0(SPMigrationAction.java:228) at java.base/java.util.Optional.ifPresent(Optional.java:183) at com.redhat.rhn.frontend.action.systems.SPMigrationAction.execute(SPMigrationAction.java:228) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) ... 47 more

2 1

Newly registered client shows last booted time = registration time
by J-M Roth 28 Sep '21

28 Sep '21

Hello, We found that for a newly registered system, Detail > Overview > System Events > Last Booted shows the time at which the system was registered/bootstrapped, and not actually booted. I opened a ticket with support, they just gave me "works as designed" because the documentation for "Overview > System Status" notes "This message indicates the current state of your system _in relation to SUSE Manager_." I fail what that is supposed to mean, especially since system status and system events are different parts of the GUI. best regards, J-M Roth

2 3

Client tools for CentOS 7 - verison issue for salt
by Cristian Gherman 28 Sep '21

28 Sep '21

Hello all @Julio I spotted again a issue with latest salt-minon packages form CentOS 7 - which on repo have a lower version as we had in 25.May From my reposync log: 2021/05/26 15:43:05 -04:00 38/54 : salt-minion-3000-20.2.uyuni.x86_64.rpm 2021/08/22 03:47:11 -04:00 36/58 : salt-minion-3000-14.1.uyuni.x86_64.rpm 2021/09/23 13:35:02 -04:00 11/25 : salt-minion-3000-16.2.uyuni.x86_64.rpm Package salt-minion-3000-20.2 which I have installed on my servers have last patch from 5 May And the current salt-minion-3000-16.2 has last patch from 19 Aug. As I see this version - salt-minion-3000-20.2 works ok with Uyuni 2021.09 My previous thread with similar isssue: https://lists.opensuse.org/archives/list/users@lists.uyuni-project.org/thre… Best Regards, -- Cristian Gherman Syasadmin @Reea | cristian.gherman(a)reea.net | www.reea.net

2 2

Some packages for the Server not bing updated during the update to Uyuni 2021.09
by Julio Gonzalez 24 Sep '21

24 Sep '21

Hello, Some users reported that some packages are not being updated on the Server during the update to Uyuni 2021.09. The cause and the workaround is now documented at: https://github.com/uyuni-project/uyuni/issues/4244 The problem is in fact that openSUSE is shipping some SUSE Manager packages, so we filled https://bugzilla.opensuse.org/show_bug.cgi?id=1190851 This announce is now posted at the website, and Twitter, and it will be part of the Release Notes for Uyuni 2021.10 if the problem is still not solved. Sorry about the inconvenience. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Uyuni 2021.09 is released!
by Julio Gonzalez 23 Sep '21

23 Sep '21

We are happy to announce the immediate availability of Uyuni 2021.09 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.09, 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: * Prometheus available for Uyuni Proxy and Retail Branch Server * Ansible available for Uyuni Proxy and Retail Branch Server * AppStreams WebUI improvements * Improve the date time handling on the UI * Support syncing patches with advisory status 'pending' * Virtualization: UEFI support: and virt-tuner templates * spacecmd: allow massive archive and delete actions * Recent cobbler CVEs remediation Please check the release notes for full details. Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2021.09 As always, we hope you will enjoy Uyuni 2021.09 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

Reminder: Uyuni Community Hours this Friday (Sep 24th) at 16.00 CEST
by Julio Gonzalez 21 Sep '21

21 Sep '21

The provisional agenda and the link to the meeting is at: https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours If you want to present, remember to send me an e-email, and we'll schedule a slot for you :-) See you on Friday! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

migrate from RMT to Uyuni while patching SLES15 SP2 systems to SP3?
by Heiner Wulfhorst 17 Sep '21

17 Sep '21

Hi list! I was asked to patch our SLES15 SP2 systems to SP3. Currently they are connected to SUSE RMT. Do you think that is a good opportunity to also migrate them into our uyuni? Pros: * I don't have to touch every system twice * am able to do any post-upgrade task faster and more easy as i have "the power of salt" Con: Double risk for incidents Or would you separate that change? -> why? I think the biggest risk lies within SP Upgrade, am i right? Is there any "compatibility check" / dry run i can do on target systems to see how they would be affected by the Upgrade before i run it? Or anything else to minimize risk? What are your thoughts about this? BR Heiner

1 0

2022

2021

2020

2019

2018

Uyuni Users September 2021