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