June 2019 - Infra - oVirt List Archives

[CQ]: 100734, 10 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100734,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100347,18 (ovirt-provider-ovn) 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 100347,18 (ovirt-provider-ovn) 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/100734/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100347/18 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1337/

1 0

[CQ]: 170e6b6 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 170e6b6 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change e09c696 (ovirt-engine-sdk-go) 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 e09c696 (ovirt-engine-sdk-go) 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://github.com/oVirt/ovirt-engine-sdk-go/commit/170e6b6e906e7c23cf5858d… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/e09c69642cf137807bb075d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1331/

1 0

oVirt infra daily report - unstable production jobs - 867
by jenkins＠jenkins.phx.ovirt.org 26 Jun '19

26 Jun '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/867//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: e09c696 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests
by oVirt Jenkins 25 Jun '19

25 Jun '19

Change e09c696 (ovirt-engine-sdk-go) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/e09c69642cf137807bb075d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1325/

1 0

[CQ]: 98030, 8 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 98030,8 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) 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 100733,12 (ovirt-provider-ovn) 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/98030/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4565/

1 0

[CQ]: 100659, 6 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100659,6 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100347,18 (ovirt-provider-ovn) 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 100347,18 (ovirt-provider-ovn) 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/100659/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100347/18 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1319/

1 0

[CQ]: 100957, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 100957,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) 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 100733,12 (ovirt-provider-ovn) 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/100957/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4563/

1 0

Fwd: [CentOS-devel] The future of the community build services
by Sandro Bonazzola 25 Jun '19

25 Jun '19

FYI ---------- Forwarded message --------- Da: Thomas Oulevey <thomas.oulevey(a)cern.ch> Date: lun 24 giu 2019 alle ore 17:21 Subject: [CentOS-devel] The future of the community build services To: <centos-devel(a)centos.org> Hi Folks, It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...). As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution. It makes sense for cbs.centos.org to follow this trend and be based on the same templates. At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches. It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly. Please let us know, if you have comments and/or new ideas. -- Thomas Oulevey [1]: https://blog.centos.org/2019/06/centos-8-status-17-june-2019/ [2]: https://github.com/puiterwijk/mbbox _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

1 0

[CQ]: 100597, 22 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 100597,22 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) 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 100733,12 (ovirt-provider-ovn) 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/100597/22 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4560/

1 0

[JIRA] (OVIRT-2742) ovirt-appliance build failure on missing module urllib.request
by Anton Marchukov (oVirt JIRA) 25 Jun '19

25 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2742?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2742: ---------------------------------------- [~sbonazzo(a)redhat.com] it looks to be controllable from STDCI project files indeed. Were you able to fix it or still need help? > ovirt-appliance build failure on missing module urllib.request > -------------------------------------------------------------- > > Key: OVIRT-2742 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2742 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > *16:16:26* Traceback (most recent call last):*16:16:26* File > "scripts/create_ova.py", line 4, in <module>*16:16:26* from > imagefactory_plugins.ovfcommon.ovfcommon import > RHEVOVFPackage*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imagefactory_plugins/ovfcommon/ovfcommon.py", > line 29, in <module>*16:16:26* from imgfac.PersistentImageManager > import PersistentImageManager*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/PersistentImageManager.py", > line 17, in <module>*16:16:26* from .ApplicationConfiguration > import ApplicationConfiguration*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/ApplicationConfiguration.py", > line 24, in <module>*16:16:26* import urllib.request*16:16:26* > ImportError: No module named request > Seen in > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x8… > https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_6… > https://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_6… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0