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

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  Sent: 21 July 2021 08:50 To: Michael Calmer ; users@lists.uyuni-project.org; Silvio Moioli 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.