- ARCHIVED: Uyuni Users

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

Recent errors syncing EL7's EPEL repo
by Simon Avery 08 Sep '21

08 Sep '21

Hi Folks, Anyone else having sync issues with EL7's EPEL repo for the past week or so? I've split out and recreated the repo on Uyuni but it still bombs out when importing one of the errata files. My hunch is this is actually an EPEL issue rather than a Uyuni one, but the pertinent error makes me wonder if this is a new thing that's going to need extra handling in Uyuni? "CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck"" Things were okay a week or so-ish ago and I made no changes on my side, but started getting sync failures late last week, or over the weekend. Thanks Example repo url; https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7/x86_64/ 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2019-3630e34c31 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2018-81bb24fe00 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2018-6f7d6eeeed 2021/09/08 13:35:47 +01:00 Syncing 4684 new patch(es) to channel. 2021/09/08 13:36:02 +01:00 Unexpected error: <class 'psycopg2.errors.CheckViolation'> 2021/09/08 13:36:02 +01:00 Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 600, in sync self.import_updates(plugin) File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 741, in import_updates processed_updates_count = self.upload_updates(notices) File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 967, in upload_updates importer.run() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/importLib.py", line 778, in run self.submit() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/errataImport.py", line 217, in submit dml = self.backend.processErrata(self.batch) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 1011, in processErrata transactional=1) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2151, in __processObjectCollection return self.__processObjectCollection__(objColl, parentTable, childDict, **kwargs) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2322, in __processObjectCollection__ return self.__doDML(dml) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2427, in __doDML self.__doInsert(dml.insert, dml.tables) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2434, in __doInsert self.__doInsertTable(tname, dict) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2449, in __doInsertTable insertObj.query(hash) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backendLib.py", line 453, in query statement.execute_values(self._buildQuery(None), value_list, fetch=False, page_size=10_000) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", line 166, in execute_values return self._execute_wrapper(self._execute_values, sql, argslist, template, page_size, fetch) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 299, in _execute_wrapper retval = function(*p, **kw) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 353, in _execute_values results = psycopg2.extras.execute_values(self._real_cursor, sql, argslist, template=template, page_size=page_size, fetch=fetch) File "/usr/lib64/python3.6/site-packages/psycopg2/extras.py", line 1289, in execute_values cur.execute(b''.join(parts)) psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (11847, FEDORA-EPEL-2021-aa19cf2506, Product Enhancement Advisory, FEDORA-EPEL-2021-aa19cf2506, 200, Fedora EPEL 7, Rebuild for Knot DNS 3.1, knot-resolver-5.4.1-2.el7, , , 2021-09-06 03:52:14-01, 2021-09-06 03:52:14-01, null, null, 1, null, updates(a)fedoraproject.org<mailto:updates@fedoraproject.org>, 2021-09-08 11:34:52.299009-01, 2021-09-08 11:34:52.299009-01, 2021-09-08 11:34:52.299009-01, 1, pending). Simon Avery Linux Systems Administrator

2 2

Packages not updated after update 2021:06 -> 2021:08
by Bidault, Philippe 06 Sep '21

06 Sep '21

Hi all ¡ I have just updated Uyuni to 2021:08, and have noticed 6 packages not being update because of a vendor change: uyuni:~ # zypper update 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. uyuni:~ # zypper update mgr-osa-dispatcher python3-mgr-osa-common python3-mgr-osa-dispatcher python3-rhnlib python3-suseRegisterInfo suseRegisterInfo Loading repository data... Reading installed packages... There is an update candidate for 'python3-rhnlib' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-rhnlib-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'suseRegisterInfo' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install suseRegisterInfo-4.3.1-1.2.uyuni1.noarch' to install this candidate. 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. There is an update candidate for 'python3-mgr-osa-common' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-mgr-osa-common-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'python3-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 python3-mgr-osa-dispatcher-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'python3-suseRegisterInfo' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-suseRegisterInfo-4.3.1-1.2.uyuni1.noarch' to install this candidate. Resolving package dependencies... Nothing to do. Do I have to change vendor for them and force the update or do I have to keep them like that ? Regards, Philippe. Philippe Bidault | Unix Engineer | Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com<https://www.getronics.com> [cid:3-lines_7512e235-163a-4853-8e4f-b0d4fc62ce73.png]<https://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: http://www.getronics.com/legal/

2 4

Problems when using server-migrator.sh to get from 2021.02 to .08
by Heiner Wulfhorst 02 Sep '21

02 Sep '21

Hi List, first i ran zypper ref and zypper up susemanager which said " *No update candidate*, *The highest available version is already installed* , Nothing to do ": # *zypper ref* Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'uyuni-server-2021-02' is up to date. *All repositories have been refreshed.* # *zypper up susemanager* Loading repository data... Reading installed packages... *No update candidate for 'susemanager-4.2.8-1.1.uyuni.x86_64'. The highest available version is already installed.* Resolving package dependencies... *Nothing to do.* But then i got this error when running /usr/lib/susemanager/bin/ server-migrator.sh (for full output see attachment): Computing distribution upgrade... 5 Problems: Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Problem: nothing provides 'libcrypt.so.1(XCRYPT_2.0)(64bit)' needed by the to be installed jabberd-sqlite-2.7.0-5.5.uyuni1.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Solution 1: Following actions will be done: deinstallation of spacewalk-postgresql-4.2.3-1.2.uyuni.noarch deinstallation of spacewalk-common-4.2.3-1.2.uyuni.noarch Solution 2: keep obsolete spacewalk-postgresql-4.2.3-1.2.uyuni.noarch Solution 3: break spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c =================================================================== If you did not yet migrate the database to postgresql12, do so now by running /usr/lib/susemanager/bin/pg-migrate-10-to-12.sh Reboot system afterwards. =================================================================== After that error i ran zypper ref and zypper up susemanager again, which (whyever) then found this update for susemanager: # zypper ref Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'Uyuni Server Stable' is up to date. All repositories have been refreshed. # zypper up susemanager Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: susemanager 1 package to upgrade. Overall download size: 83.8 KiB. Already cached: 0 B. After the operation, additional 14.0 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package susemanager-4.3.2-1.1.uyuni1.x86_64 (1/1), 83.8 KiB (197.6 KiB unpacked) Retrieving: susemanager-4.3.2-1.1.uyuni1.x86_64.rpm .............................................................................................[done] Checking for file conflicts: ....................................................................................................................[done] (1/1) Installing: susemanager-4.3.2-1.1.uyuni1.x86_64 ...........................................................................................[done] Executing %posttrans scripts ....................................................................................................................[done] After that i ran /usr/lib/susemanager/bin/server-migrator.sh again which then returned no more errors/problems and began to upgrade my system: <...> Executing %posttrans scripts ....................................................................................................................[done] Update notifications were received from the following packages: susemanager-schema-4.3.1-1.2.uyuni1.noarch (/var/adm/update-messages/susemanager-schema-4.3.1-1.2.uyuni1) View the notifications now? [y/n] (n): n There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs. Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates. =================================================================== If you did not yet migrate the database to postgresql13, do so now by running /usr/lib/susemanager/bin/pg-migrate-x-to-y.sh Reboot system afterwards. =================================================================== What went wrong? Is there an error in the upgrade guide ( https://www.uyuni-project.org/doc/2021.08/uyuni_upgrade_guide.pdf)? Looks like at first try it is using leap/15.2 repos and at second try 15.3... BR, Heiner

2 4