Error while syncing EPEL 8 repository
Hello, Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation): 2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in. 2021/07/11 -> first error appears psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35-02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021-07- 10 22:02:40.365219-02, null). 2021/07/19 -> the same with different data psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending, Fedora EPEL 8, Initial package, python-nagiosplugin-1.3.2- 1.el8, , , 2021-07-18 17:55:58-02, 2021-07-18 17:55:58-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-19 04:22:00.854661- 02, 2021-07-19 04:22:00.854661-02, 2021-07-19 04:22:00.854661-02, null). 2021/07/21 -> third occurrence, this time repeating "python- nagiosplugin" instance. psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8735, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending, Fedora EPEL 8, Initial package, python-nagiosplugin-1.3.2- 1.el8, , , 2021-07-18 17:55:58-02, 2021-07-18 17:55:58-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-19 22:02:34.756984- 02, 2021-07-19 22:02:34.756984-02, 2021-07-19 22:02:34.756984-02, null). This is from last night: psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8752, FEDORA-EPEL-2021-a5a0c05adf, Product Enhancement Advisory, FEDORA-EPEL-2021-a5a0c05adf, 200, pending, Fedora EPEL 8, Initial package, python-jdcal-1.4.1-1.el8, , , 2021-07-19 16:46:28-02, 2021-07-19 16:46:28-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-20 04:05:53.484279-02, 2021-07-20 04:05:53.484279-02, 2021-07-20 04:05:53.484279-02, null). Full log: # LANG=C spacewalk-repo-sync -c epel8-almalinux8-x86_64 08:46:02 ====================================== 08:46:02 | Channel: epel8-almalinux8-x86_64 08:46:02 ====================================== 08:46:02 Sync of channel started. Retrieving repository 'epel8-almalinux8-x86_64' metadata ...............................[done] Building repository 'epel8-almalinux8-x86_64' cache ....................................[done] All repositories have been refreshed. 08:46:06 08:46:06 Importing comps file 96d01da780a309a1803ea903a9f2a33b1c239a265847c6a86718acb9ef85f06e-comps- Everything.x86_64.xml. 08:46:06 Renaming non-standard filename 96d01da780a309a1803ea903a9f2a33b1c239a265847c6a86718acb9ef85f06e-comps- Everything.x86_64.xml to comps.x86_64.xml. 08:46:06 *** NOTE: Importing comps file for the channel 'epel8- almalinux8-x86_64'. Previous comps will be discarded. 08:46:06 Repo URL: https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/ 08:46:06 Packages in repo: 7558 08:46:14 No new packages to sync. 08:46:15 08:46:15 Patches in repo: 3017. 08:46:15 Add Patch FEDORA-EPEL-2021-3ec3998292 08:46:16 Add Patch FEDORA-EPEL-2021-7dc78a18ca 08:46:16 Add Patch FEDORA-EPEL-2021-d33da662e7 08:46:16 Add Patch FEDORA-EPEL-2021-87b303b50e 08:46:17 Add Patch FEDORA-EPEL-2021-7ed6a63b7b 08:46:17 Add Patch FEDORA-EPEL-2021-a5a0c05adf 08:46:17 Add Patch FEDORA-EPEL-2021-f77315a931 08:46:17 Add Patch FEDORA-EPEL-2021-333cf44938 08:46:17 Add Patch FEDORA-EPEL-2021-fdb6cf1e3a 08:46:17 Add Patch FEDORA-EPEL-2021-b3771b0cd1 08:46:18 Add Patch FEDORA-EPEL-2021-15c5b7660c 08:46:18 Add Patch FEDORA-EPEL-2021-384d2492fa 08:46:18 Add Patch FEDORA-EPEL-2021-247500b671 08:46:18 Add Patch FEDORA-EPEL-2021-d4c3bbff96 08:46:19 Add Patch FEDORA-EPEL-2021-a60d1222d2 08:46:19 Add Patch FEDORA-EPEL-2021-ec70035a87 08:46:19 Add Patch FEDORA-EPEL-2021-d48e8d2d55 08:46:19 Add Patch FEDORA-EPEL-2021-293195e59b 08:46:19 Add Patch FEDORA-EPEL-2021-41eeae14d9 08:46:19 Add Patch FEDORA-EPEL-2021-ec2a0a616a 08:46:19 Add Patch FEDORA-EPEL-2021-b8960f6143 08:46:19 Add Patch FEDORA-EPEL-2021-20a66b3776 08:46:20 Add Patch FEDORA-EPEL-2020-7c3fde7f74 08:46:20 Add Patch FEDORA-EPEL-2021-ac096c00b0 08:46:20 Add Patch FEDORA-EPEL-2021-aa67d44d29 08:46:20 Add Patch FEDORA-EPEL-2021-d3d8cfc98d 08:46:20 Syncing 25 new patch(es) to channel. 08:46:20 Unexpected error: <class 'psycopg2.errors.CheckViolation'> 08:46:20 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 (8816, FEDORA-EPEL-2021-a5a0c05adf, Product Enhancement Advisory, FEDORA-EPEL-2021-a5a0c05adf, 200, pending, Fedora EPEL 8, Initial package, python-jdcal-1.4.1-1.el8, , , 2021-07-19 16:46:28-02, 2021-07-19 16:46:28-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-20 04:46:02.984641-02, 2021-07-20 04:46:02.984641-02, 2021-07-20 04:46:02.984641-02, null). 08:46:20 Total time: 0:00:17 Any ideas ? Thank you, Jordi.
On 20/07/2021 08.51, jordi@priscoelectronica.com wrote:
Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation):
2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in.
2021/07/11 -> first error appears
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35-02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021-07- 10 22:02:40.365219-02, null).
2021/07/19 -> the same with different data
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending
It seems like there is a new errata status, 'pending', that we did not know. Indeed we have a check that says: advisory_status VARCHAR(32) NOT NULL DEFAULT('final') CONSTRAINT rhn_errata_adv_status_ck CHECK (advisory_status in ('final', 'stable', 'testing', 'retracted')), As you can see "pending" is not in the allowed set ('final', 'stable', 'testing', 'retracted'). Michael: is it just a matter of relaxing the check, or do we have to do anything else with that status? Regards, -- Silvio Moioli SUSE Manager Development Team
Hi Am Dienstag, 20. Juli 2021, 10:48:27 CEST schrieb Silvio Moioli:
On 20/07/2021 08.51, jordi@priscoelectronica.com wrote:
Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation):
2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in.
2021/07/11 -> first error appears
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35-02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021-07- 10 22:02:40.365219-02, null).
2021/07/19 -> the same with different data
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending
It seems like there is a new errata status, 'pending', that we did not know. Indeed we have a check that says:
advisory_status VARCHAR(32) NOT NULL DEFAULT('final') CONSTRAINT rhn_errata_adv_status_ck CHECK (advisory_status in ('final', 'stable', 'testing', 'retracted')),
As you can see "pending" is not in the allowed set ('final', 'stable', 'testing', 'retracted').
Michael: is it just a matter of relaxing the check, or do we have to do anything else with that status?
AFAIK we need this also in the Java code as we have an enum with the states there as well. As you know we react on "retracted" with some special handling. The question is: what does "pending" mean? Do you want to see "pending" errata in the metadata for the clients or not? So we could simply passthru the data like for final, stable or we can do something special. -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
El dt. 20 de 07 de 2021 a les 11:00 +0200, en/na Michael Calmer va escriure: Hello, I've just opened a bugreport. https://github.com/uyuni-project/uyuni/issues/4011 Thank you for your help on this. regards, Jordi.
Hi
Am Dienstag, 20. Juli 2021, 10:48:27 CEST schrieb Silvio Moioli:
On 20/07/2021 08.51, jordi@priscoelectronica.com wrote:
Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation):
2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in.
2021/07/11 -> first error appears
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35- 02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021- 07- 10 22:02:40.365219-02, null).
2021/07/19 -> the same with different data
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending
It seems like there is a new errata status, 'pending', that we did not know. Indeed we have a check that says:
advisory_status VARCHAR(32) NOT NULL DEFAULT('final') CONSTRAINT rhn_errata_adv_status_ck CHECK (advisory_status in ('final', 'stable', 'testing', 'retracted')),
As you can see "pending" is not in the allowed set ('final', 'stable', 'testing', 'retracted').
Michael: is it just a matter of relaxing the check, or do we have to do anything else with that status?
AFAIK we need this also in the Java code as we have an enum with the states there as well. As you know we react on "retracted" with some special handling. The question is: what does "pending" mean? Do you want to see "pending" errata in the metadata for the clients or not?
So we could simply passthru the data like for final, stable or we can do something special.
Hi Jordi, This possibly doesn't help much, but I'm NOT seeing the same issue when syncing Epel for Centos-8 or Rocky-8 (same repo included in different channels) It's behaving normally here. Will add a note to the issue as well, in case it helps the devs. 2021/03/21 14:00:13 +01:00 Repo URL: http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/8/Everythin... 2021/03/21 14:00:13 +01:00 Packages in repo: 7121 2021/03/21 14:00:27 +01:00 Packages already synced: 6941 2021/03/21 14:00:27 +01:00 Packages to sync: 180 2021/03/21 14:00:27 +01:00 New packages to download: 180 2021/03/21 14:00:27 +01:00 Downloading packages: 2021/03/21 14:00:28 +01:00 1/180 : asciinema-2.0.2-6.el8.noarch.rpm 2021/03/21 14:00:28 +01:00 2/180 : distribution-gpg-keys-1.51-1.el8.noarch.rpm ... 2021/03/21 14:00:41 +01:00 180/180 : zabbix40-web-4.0.29-1.el8.noarch.rpm 2021/03/21 14:00:41 +01:00 Importing packages started. 2021/03/21 14:00:41 +01:00 2021/03/21 14:00:41 +01:00 Importing packages to DB: 2021/03/21 14:00:45 +01:00 Package batch #3 of 9 completed... ... 2021/03/21 14:01:11 +01:00 Package batch #8 of 9 completed... 2021/03/21 14:01:11 +01:00 Importing packages finished. 2021/03/21 14:01:11 +01:00 ... 2021/07/21 08:38:27 +01:00 Linking packages to the channel. 2021/07/21 08:38:28 +01:00 34 packages linked 2021/07/21 08:38:29 +01:00 2021/07/21 08:38:29 +01:00 Patches in repo: 3018. 2021/07/21 08:38:30 +01:00 Add Patch FEDORA-EPEL-2021-762ccf9ade 2021/07/21 08:38:31 +01:00 Add Patch FEDORA-EPEL-2021-a60d1222d2 2021/07/21 08:38:31 +01:00 Add Patch FEDORA-EPEL-2021-aa67d44d29 2021/07/21 08:38:34 +01:00 Add Patch FEDORA-EPEL-2021-ec2a0a616a 2021/07/21 08:38:35 +01:00 Add Patch FEDORA-EPEL-2020-7c3fde7f74 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-7ed6a63b7b 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-41eeae14d9 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-9ba6d5793a 2021/07/21 08:38:37 +01:00 Add Patch FEDORA-EPEL-2021-a5a0c05adf 2021/07/21 08:38:37 +01:00 Add Patch FEDORA-EPEL-2021-ec70035a87 2021/07/21 08:38:37 +01:00 Syncing 9 new patch(es) to channel. 2021/07/21 08:38:41 +01:00 2021/07/21 08:38:41 +01:00 Importing comps file bbe4d6c0eadd96f6a033794a25f89a2df43e5a02007f8fe748ef7634099bcbbc-comps-BaseOS.x86_64.xml. 2021/07/21 08:38:41 +01:00 Renaming non-standard filename bbe4d6c0eadd96f6a033794a25f89a2df43e5a02007f8fe748ef7634099bcbbc-comps-BaseOS.x86_64.xml to comps.x86_64.xml. -----Original Message----- From: jordi@priscoelectronica.com <jordi@priscoelectronica.com> Sent: 21 July 2021 08:50 To: Michael Calmer <mc@suse.de>; users@lists.uyuni-project.org; Silvio Moioli <moio@suse.com> Subject: [EXTERNAL EMAIL] Re: Error while syncing EPEL 8 repository El dt. 20 de 07 de 2021 a les 11:00 +0200, en/na Michael Calmer va escriure: Hello, I've just opened a bugreport. https://github.com/uyuni-project/uyuni/issues/4011 Thank you for your help on this. regards, Jordi.
Hi
Am Dienstag, 20. Juli 2021, 10:48:27 CEST schrieb Silvio Moioli:
On 20/07/2021 08.51, jordi@priscoelectronica.com wrote:
Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation):
2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in.
2021/07/11 -> first error appears
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35- 02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021- 07- 10 22:02:40.365219-02, null).
2021/07/19 -> the same with different data
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending
It seems like there is a new errata status, 'pending', that we did not know. Indeed we have a check that says:
advisory_status VARCHAR(32) NOT NULL DEFAULT('final') CONSTRAINT rhn_errata_adv_status_ck CHECK (advisory_status in ('final', 'stable', 'testing', 'retracted')),
As you can see "pending" is not in the allowed set ('final', 'stable', 'testing', 'retracted').
Michael: is it just a matter of relaxing the check, or do we have to do anything else with that status?
AFAIK we need this also in the Java code as we have an enum with the states there as well. As you know we react on "retracted" with some special handling. The question is: what does "pending" mean? Do you want to see "pending" errata in the metadata for the clients or not?
So we could simply passthru the data like for final, stable or we can do something special.
El dj. 22 de 07 de 2021 a les 09:40 +0000, en/na Simon Avery va escriure: Hello Simon, I think this kind of error is something that happens sometime. While a patch is considered 'pending', you will see this error because of the sql constraint. Later on, this patch is no longer classified as 'pending', EPEL repo is regenerated and then it syncs correctly. It was not producing an error everyday on my site either. regards,
Hi Jordi,
This possibly doesn't help much, but I'm NOT seeing the same issue when syncing Epel for Centos-8 or Rocky-8 (same repo included in different channels)
It's behaving normally here. Will add a note to the issue as well, in case it helps the devs.
2021/03/21 14:00:13 +01:00 Repo URL: http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/8/Everythin... 2021/03/21 14:00:13 +01:00 Packages in repo: 7121 2021/03/21 14:00:27 +01:00 Packages already synced: 6941 2021/03/21 14:00:27 +01:00 Packages to sync: 180 2021/03/21 14:00:27 +01:00 New packages to download: 180 2021/03/21 14:00:27 +01:00 Downloading packages: 2021/03/21 14:00:28 +01:00 1/180 : asciinema-2.0.2- 6.el8.noarch.rpm 2021/03/21 14:00:28 +01:00 2/180 : distribution-gpg-keys-1.51- 1.el8.noarch.rpm
...
2021/03/21 14:00:41 +01:00 180/180 : zabbix40-web-4.0.29- 1.el8.noarch.rpm 2021/03/21 14:00:41 +01:00 Importing packages started. 2021/03/21 14:00:41 +01:00 2021/03/21 14:00:41 +01:00 Importing packages to DB: 2021/03/21 14:00:45 +01:00 Package batch #3 of 9 completed...
...
2021/03/21 14:01:11 +01:00 Package batch #8 of 9 completed... 2021/03/21 14:01:11 +01:00 Importing packages finished. 2021/03/21 14:01:11 +01:00
...
2021/07/21 08:38:27 +01:00 Linking packages to the channel. 2021/07/21 08:38:28 +01:00 34 packages linked 2021/07/21 08:38:29 +01:00 2021/07/21 08:38:29 +01:00 Patches in repo: 3018. 2021/07/21 08:38:30 +01:00 Add Patch FEDORA-EPEL-2021-762ccf9ade 2021/07/21 08:38:31 +01:00 Add Patch FEDORA-EPEL-2021-a60d1222d2 2021/07/21 08:38:31 +01:00 Add Patch FEDORA-EPEL-2021-aa67d44d29 2021/07/21 08:38:34 +01:00 Add Patch FEDORA-EPEL-2021-ec2a0a616a 2021/07/21 08:38:35 +01:00 Add Patch FEDORA-EPEL-2020-7c3fde7f74 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-7ed6a63b7b 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-41eeae14d9 2021/07/21 08:38:36 +01:00 Add Patch FEDORA-EPEL-2021-9ba6d5793a 2021/07/21 08:38:37 +01:00 Add Patch FEDORA-EPEL-2021-a5a0c05adf 2021/07/21 08:38:37 +01:00 Add Patch FEDORA-EPEL-2021-ec70035a87 2021/07/21 08:38:37 +01:00 Syncing 9 new patch(es) to channel. 2021/07/21 08:38:41 +01:00 2021/07/21 08:38:41 +01:00 Importing comps file bbe4d6c0eadd96f6a033794a25f89a2df43e5a02007f8fe748ef7634099bcbbc- comps-BaseOS.x86_64.xml. 2021/07/21 08:38:41 +01:00 Renaming non-standard filename bbe4d6c0eadd96f6a033794a25f89a2df43e5a02007f8fe748ef7634099bcbbc- comps-BaseOS.x86_64.xml to comps.x86_64.xml.
-----Original Message----- From: jordi@priscoelectronica.com <jordi@priscoelectronica.com> Sent: 21 July 2021 08:50 To: Michael Calmer <mc@suse.de>; users@lists.uyuni-project.org; Silvio Moioli <moio@suse.com> Subject: [EXTERNAL EMAIL] Re: Error while syncing EPEL 8 repository
El dt. 20 de 07 de 2021 a les 11:00 +0200, en/na Michael Calmer va escriure:
Hello,
I've just opened a bugreport.
https://github.com/uyuni-project/uyuni/issues/4011
Thank you for your help on this.
regards,
Jordi.
Hi
Am Dienstag, 20. Juli 2021, 10:48:27 CEST schrieb Silvio Moioli:
On 20/07/2021 08.51, jordi@priscoelectronica.com wrote:
repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation):
2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in.
2021/07/11 -> first error appears
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021- 360b258add, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35- 02, 2021-07-09 07:48:52-02, null, null, 1, null, updates@fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021- 07- 10 22:02:40.365219-02, null).
2021/07/19 -> the same with different data
psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021- 41eeae14d9, pending
It seems like there is a new errata status, 'pending', that we did not know. Indeed we have a check that says:
advisory_status VARCHAR(32) NOT NULL DEFAULT('final') CONSTRAINT rhn_errata_adv_status_ck 'stable', 'testing', 'retracted')),
As you can see "pending" is not in the allowed set ('final', 'stable', 'testing', 'retracted').
Michael: is it just a matter of relaxing the check, or do we have to do anything else with that status?
AFAIK we need this also in the Java code as we have an enum with the states there as well. question is: what does "pending" mean? Do you want to see "pending" errata in the metadata for the clients or not?
So we could simply passthru the data like for final, stable or we can do something special.
participants (4)
-
jordi＠priscoelectronica.com -
Michael Calmer -
Silvio Moioli -
Simon Avery