March 2018 - Infra - oVirt List Archives

ovirt-engine_4.2_check-patch-fc27-x86_64 fails
by Dominik Holler 12 Mar '18

12 Mar '18

Hi, dnf in CI jobs ovirt-engine_4.2_check-patch-fc27-x86_64 [1] is failing for me with: ImportError: libelf.so.1: cannot open shared object file: No such file or directory Can you please have a look? Thanks Dominik [1] http://jenkins.ovirt.org/job/ovirt-engine_4.2_check-patch-fc27-x86_64/411 12:48:21 Start: dnf install 12:48:22 ERROR: Command failed: 12:48:22 # /usr/bin/dnf --installroot /var/lib/mock/fedora-27-x86_64-27659b1e362bd3ee3ef0da8cd3f0c97c-26540/root/ --releasever 27 --disableplugin=local --setopt=deltarpm=False install @buildsys-build libcrypt-nss autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server postgresql-contrib pyflakes python2-mock python2-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts 12:48:22 Traceback (most recent call last): 12:48:22 File "/usr/bin/dnf", line 57, in <module> 12:48:22 from dnf.cli import main 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/__init__.py", line 31, in <module> 12:48:22 import dnf.base 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/base.py", line 29, in <module> 12:48:22 from dnf.yum import history 12:48:22 File "/usr/lib/python3.6/site-packages/dnf/yum/history.py", line 22, in <module> 12:48:22 import hawkey 12:48:22 File "/usr/lib64/python3.6/site-packages/hawkey/__init__.py", line 24, in <module> 12:48:22 from . import _hawkey 12:48:22 ImportError: libelf.so.1: cannot open shared object file: No such file or directory

2 1

[CQ]: 88580, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88580,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88580/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6252/

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Yedidyah Bar David (oVirt JIRA) 12 Mar '18

12 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1926?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1926: ------------------------------------------- On Mon, Mar 12, 2018 at 2:09 PM, Barak Korren (oVirt JIRA) < Not sure what you mean. I already wrote that there was no code change. But there definitely was a _squash_. So the git history was very different. Patchsets 7 and 8 had different parents. Fine, so you mean I should file a bug against gerrit itself? OK: https://bugs.chromium.org/p/gerrit/issues/detail?id=8521 -- Didi > squash identified as a mere message update > ------------------------------------------ > > Key: OVIRT-1926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Barak Korren (oVirt JIRA) 12 Mar '18

12 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1926?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1926: ------------------------------------- I don't think it has to do with [1], looking in Gerrit, there does not seem to be any code difference between patchsets 7 and 8 of [2]. In any case this Gerrit behaviour is not something any code we maintain does. > squash identified as a mere message update > ------------------------------------------ > > Key: OVIRT-1926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

2 1

[CQ]: 88764, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88764,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88738,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88764/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1198/

1 0

[JIRA] (OVIRT-1926) squash identified as a mere message update
by Yedidyah Bar David (oVirt JIRA) 12 Mar '18

12 Mar '18

Yedidyah Bar David created OVIRT-1926: ----------------------------------------- Summary: squash identified as a mere message update Key: OVIRT-1926 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1926 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra I had [1] and [2]. Patchset 8 of [2] is a combination of: - Patchset 7 of it, - [1] squashed into it, - Commit message change. Gerrit commented: Uploaded patch set 8: Commit message was updated. In theory it was right, because there was no code change between 7 and 8. But I'd expect it to either be silent, or to notice that there was also a squash (and suggest to abandon the squashed patch?). [1] https://gerrit.ovirt.org/#/c/88669/ [2] https://gerrit.ovirt.org/#/c/88634/ -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[CQ]: 88362, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88362,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88620,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88620,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88362/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88620/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6249/

1 0

[CQ]: 88718, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88718,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88738,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88718/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1196/

1 0

[CQ]: 88717, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '18

12 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88717,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88738,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 88738,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/88717/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88738/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1195/

1 0

standard CI packages files
by Yedidyah Bar David 12 Mar '18

12 Mar '18

Hi all, The various automation/*.packages* files are rather hard to maintain - with many partial duplicates, symlinks, and changes applied to some file forgotten to be applied to others that needed them. Can we have something more dynamic? E.g. that CI will run a single script, e.g. automation/get-needed-packages, provide it as args the action to be ran ("check-patch", "build-artifacts" etc.) and the distro ("el7", "fc27" etc.) and use whatever it outputs as the list of packages to install? Thanks, -- Didi

2 3