Hi, the important error message is : 2018-08-31 08:16:33,302-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20180831081601-s0d22q.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0280_add_clean_traffic_gateway_into_nwfilters.sql:1: ERROR: duplicate key value violates unique constraint "network_filter_pkey" DETAIL: Key (filter_name)=(clean-traffic-gateway) already exists. FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0280_add_clean_traffic_gateway_into_nwfilters.sql The problematic script was merged into master on Aug 1st as a part of [1] and it contains: INSERT INTO network_filter VALUES (uuid_generate_v1(), 'clean-traffic-gateway' , '4.3'); It looks correct, unfortunately the patch [1] was backported into 4.2 as [2] on Aug 30th and the backport contains altered script: INSERT INTO network_filter VALUES (uuid_generate_v1(), 'clean-traffic-gateway' , '4.2'); The problem is that primary key of network_filter table is filter_name, that's why upgrade from 4.2 to 4.3 started to fail. There was an attempt to align versions in [3], but this can't help the upgrade issue as dbscript from [3] is executed after script [2], which fails the upgrade. If I understand the the logic of network_filter table, it should contain the filter name for the 1st version where it's supported. So I've posted the fix for upgrade issue here [4]. Ales/Dominik could you please review? Thanks Martin [1] https://gerrit.ovirt.org/93109 [2] https://gerrit.ovirt.org/93807 [3] https://gerrit.ovirt.org/93836 [4] https://gerrit.ovirt.org/94080 On Fri, Aug 31, 2018 at 11:34 AM, Anton Marchukov <amarchuk@redhat.com> wrote:

I also see the following:

http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

this is the internal lago web server. Might be related, but strange that we got "Engine schema refresh failed" as a result. Might be some error checking is missing?

Anton.

On Fri, Aug 31, 2018 at 11:16 AM Anton Marchukov <amarchuk@redhat.com> wrote:

...

Hello All.

We have a failure in OST master. The link to job:

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/

and to the output:

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/testRepor...

It seems like schema fails to apply during upgrade:

File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed

I think the patch referred by the job is not the cause as ovirt-ansible-engine-setup has only release bumps recently as I see.

I will reply here if I find a probably cause.

-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ message/YJHRN5776K62HYYUPMBG5S46DFDYNHAP/

-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.