September 2021 - ARCHIVED: Uyuni Users

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