February 2019 - Infra - oVirt List Archives

[CQ]: 97561, 2 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97561,2 (ovirt-engine-ui-extensions) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97561/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12679/

1 0

oVirt infra daily report - unstable production jobs - 727
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '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/727//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97532,2 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97532,2 (ovirt-appliance) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97532/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12674/

1 0

[CQ]: 88c6916 (ovirt-ansible-infra) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 88c6916 (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-master" 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-ansible-infra/commit/88c6916af18b01228c7823e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12669/

1 0

[CQ]: 97479,7 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97479,7 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97479/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12664/

1 0

[CQ]: 97437, 6 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97437,6 (ovirt-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97437/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12659/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3440 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-msx6n.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3440 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-q0s3t.

1 0

[CQ]: 96974fa (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '19

05 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96974fa (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 9267118 (ovirt-ansible- hosted-engine-setup) 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 9267118 (ovirt-ansible-hosted- engine-setup) 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-ansible-hosted-engine-setup/commit/96974fad1… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/9267118f4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12655/

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2666: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2666: ---------------------------------- Galit merged a fix and upstream is fix. Closing this as resolved. Please re-open if this is still happening for you. > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2669: ------------------------------- Resolution: Duplicate Status: Done (was: To Do) > CI scripts try to modify unrelated bugs > --------------------------------------- > > Key: OVIRT-2669 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > If a commit message mention another bug, the CI script try to add the patch > to the bug in the commit message, and change the bug to POST. > Mentioning another bug in a commit message is good practice, making it > easier to follow, and avoiding unclear forms like "bug 1000000" or > "BZ#1000000", > or even worse shortened urls like https://goo.gl/bPuFGo. > Does it make sense that we cannot link to Red Hat bugzilla like god > intended? > Here is a proof: > https://gerrit.ovirt.org/c/97568/ > gerrit-hooks > Patch Set 1: > Check Bug-Url::10000000::WARN, failed to get bug info (private bug or > bug doesn't exist > Check Product::IGNORE, not relevant for branch: master > Check TM::IGNORE, not relevant for branch: master > Check Backport::IGNORE, not relevant for branch: master > Set POST::#10000000::WARN, failed to get bug info (private bug or bug > doesn't exist) > Update Tracker::#10000000::WARN, failed to get bug info (private bug or > bug doesn't exist) > CI scripts should process urls only inside Bug-Url: tag. > Expected behavior: > Extract bug urls *only* from Bug-Url: label. > The same issue exists with Related-To: label. > This is not a new bug. I reported it few years ago but for some reason the > issue > was not understood. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2669: ------------------------------------ Closing this ticket, opening in d/s jira. > CI scripts try to modify unrelated bugs > --------------------------------------- > > Key: OVIRT-2669 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > If a commit message mention another bug, the CI script try to add the patch > to the bug in the commit message, and change the bug to POST. > Mentioning another bug in a commit message is good practice, making it > easier to follow, and avoiding unclear forms like "bug 1000000" or > "BZ#1000000", > or even worse shortened urls like https://goo.gl/bPuFGo. > Does it make sense that we cannot link to Red Hat bugzilla like god > intended? > Here is a proof: > https://gerrit.ovirt.org/c/97568/ > gerrit-hooks > Patch Set 1: > Check Bug-Url::10000000::WARN, failed to get bug info (private bug or > bug doesn't exist > Check Product::IGNORE, not relevant for branch: master > Check TM::IGNORE, not relevant for branch: master > Check Backport::IGNORE, not relevant for branch: master > Set POST::#10000000::WARN, failed to get bug info (private bug or bug > doesn't exist) > Update Tracker::#10000000::WARN, failed to get bug info (private bug or > bug doesn't exist) > CI scripts should process urls only inside Bug-Url: tag. > Expected behavior: > Extract bug urls *only* from Bug-Url: label. > The same issue exists with Related-To: label. > This is not a new bug. I reported it few years ago but for some reason the > issue > was not understood. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3436 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xxlnf.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3433 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-n1p89.

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Nir Soffer (oVirt JIRA) 05 Feb '19

05 Feb '19

Nir Soffer created OVIRT-2669: --------------------------------- Summary: CI scripts try to modify unrelated bugs Key: OVIRT-2669 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra If a commit message mention another bug, the CI script try to add the patch to the bug in the commit message, and change the bug to POST. Mentioning another bug in a commit message is good practice, making it easier to follow, and avoiding unclear forms like "bug 1000000" or "BZ#1000000", or even worse shortened urls like https://goo.gl/bPuFGo. Does it make sense that we cannot link to Red Hat bugzilla like god intended? Here is a proof: https://gerrit.ovirt.org/c/97568/ gerrit-hooks Patch Set 1: Check Bug-Url::10000000::WARN, failed to get bug info (private bug or bug doesn't exist Check Product::IGNORE, not relevant for branch: master Check TM::IGNORE, not relevant for branch: master Check Backport::IGNORE, not relevant for branch: master Set POST::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) Update Tracker::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) CI scripts should process urls only inside Bug-Url: tag. Expected behavior: Extract bug urls *only* from Bug-Url: label. The same issue exists with Related-To: label. This is not a new bug. I reported it few years ago but for some reason the issue was not understood. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

CI scripts try to modify unrelated bugs
by Nir Soffer 05 Feb '19

05 Feb '19

If a commit message mention another bug, the CI script try to add the patch to the bug in the commit message, and change the bug to POST. Mentioning another bug in a commit message is good practice, making it easier to follow, and avoiding unclear forms like "bug 1000000" or "BZ#1000000", or even worse shortened urls like https://goo.gl/bPuFGo. Does it make sense that we cannot link to Red Hat bugzilla like god intended? Here is a proof: https://gerrit.ovirt.org/c/97568/ gerrit-hooks Patch Set 1: Check Bug-Url::10000000::WARN, failed to get bug info (private bug or bug doesn't exist Check Product::IGNORE, not relevant for branch: master Check TM::IGNORE, not relevant for branch: master Check Backport::IGNORE, not relevant for branch: master Set POST::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) Update Tracker::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) CI scripts should process urls only inside Bug-Url: tag. Expected behavior: Extract bug urls *only* from Bug-Url: label. The same issue exists with Related-To: label. This is not a new bug. I reported it few years ago but for some reason the issue was not understood. Nir

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2668: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo > ------------------------------------------------------------------------- > > Key: OVIRT-2668 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Martin Perina > Assignee: Ehud Yonasi > > Hi, > I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. > Is it some issue with stdci.yaml or something went wrong in CQ publishing? > The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2668: ------------------------------------ Hi [~mwperina], It was published into master CQ, but since there was a packaging issue that was solved today, all master cq jobs failed. I've re-added your patch into the cq system and if it passes CQ, it should be published to tested. > WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo > ------------------------------------------------------------------------- > > Key: OVIRT-2668 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Martin Perina > Assignee: infra > > Hi, > I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. > Is it some issue with stdci.yaml or something went wrong in CQ publishing? > The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Martin Perina (oVirt JIRA) 05 Feb '19

05 Feb '19

Martin Perina created OVIRT-2668: ------------------------------------ Summary: WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo Key: OVIRT-2668 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Martin Perina Assignee: infra Hi, I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. Is it some issue with stdci.yaml or something went wrong in CQ publishing? The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] Thanks Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #269
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/26…> Changes: [Sandro Bonazzola] ovirt-release: move to check-patch to v2 ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 0c58c6af77462077362709504192b5388a90f207 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0c58c6af77462077362709504192b5388a90f207 Commit message: "ovirt-release: move to check-patch to v2" > git rev-list --no-walk 2475ed85fd8420315ce9833bd51cc956f7bda7e8 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins8359310665409060836.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML + reposync_out='Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64 error was 16: error opening file from https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64, IOError: [Errno 2] No such file or directory: '\''/home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml.tmp'\''' Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 726
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '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/726//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 88c6916 (ovirt-ansible-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 88c6916 (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-4.2" 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-ansible-infra/commit/88c6916af18b01228c7823e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3826/

1 0

Change in barak-test[master]: jenkins integ test
by review＠gerrit-staging.phx.ovirt.org 04 Feb '19

04 Feb '19

From Evgheni Dereveanchin <ederevea(a)redhat.com>: Evgheni Dereveanchin has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/17 ) Change subject: jenkins integ test ...................................................................... Patch Set 1: one more test -- To view, visit https://gerrit-staging.phx.ovirt.org/17 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I50acc69c8c5b6b3e03f3ced23d72c883ac4db2c2 Gerrit-Change-Number: 17 Gerrit-PatchSet: 1 Gerrit-Owner: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 04 Feb 2019 18:30:09 +0000 Gerrit-HasComments: No

1 0

[CQ]: 97547,1 (ovirt-release) failed "ovirt-4.2" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97547,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://gerrit.ovirt.org/#/c/97547/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3825/

1 0

[CQ]: 88c6916 (ovirt-ansible-infra) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 88c6916 (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-master" 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-ansible-infra/commit/88c6916af18b01228c7823e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12646/

1 0

[JIRA] (OVIRT-2667) update PHX oVirt setup to 4.3
by Evgheni Dereveanchin (oVirt JIRA) 04 Feb '19

04 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2667?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2667: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > update PHX oVirt setup to 4.3 > ----------------------------- > > Key: OVIRT-2667 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2667 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > oVirt 4.3.0 is out with lots of improvements, time to upgrade the PHX environment to this version. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97532,2 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97532,2 (ovirt-appliance) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97532/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12644/

1 0

[CQ]: 97530, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Feb '19

04 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97530,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97013,3 (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 97013,3 (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/97530/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97013/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12642/

1 0

[CQ]: 97380, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Feb '19

04 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97380,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97013,3 (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 97013,3 (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/97380/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97013/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12641/

1 0

[JIRA] (OVIRT-2667) update PHX oVirt setup to 4.3
by Evgheni Dereveanchin (oVirt JIRA) 04 Feb '19

04 Feb '19

Evgheni Dereveanchin created OVIRT-2667: ------------------------------------------- Summary: update PHX oVirt setup to 4.3 Key: OVIRT-2667 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2667 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra oVirt 4.3.0 is out with lots of improvements, time to upgrade the PHX environment to this version. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97440, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97440,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97440/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12639/

1 0

[ANN] oVirt 4.3.0 is now generally available
by Sandro Bonazzola 04 Feb '19

04 Feb '19

The oVirt Project is excited to announce the general availability of oVirt 4.3.0, as of February 4th, 2019 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses over four hundreds individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. If you’re managing more than one oVirt instance, OpenShift Origin or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such case, please ensure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS 7 and Fedora 28 - oVirt Node NG is already available for CentOS 7 and Fedora 28 [2] - oVirt Windows Guest Tools iso is already available [2] Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.0/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[CQ]: 97519,2 (ovirt-node-ng-image) failed "ovirt-4.3" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97519,2 (ovirt-node-ng-image) 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://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/14/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-qemu-ev-release-el7-x86_64 #1755
by jenkins＠jenkins.phx.ovirt.org 04 Feb '19

04 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 2475ed85fd8420315ce9833bd51cc956f7bda7e8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2475ed85fd8420315ce9833bd51cc956f7bda7e8 Commit message: "vcredist-x86: move to oVirt stdci v2" > git rev-list --no-walk 2475ed85fd8420315ce9833bd51cc956f7bda7e8 # timeout=10 [system-sync_mirrors-centos-qemu-ev-release-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5627783457335774698.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-qemu-ev-release-el7 yum + local repo_name=centos-qemu-ev-release-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-qemu-ev-release-el7 /var/www/html/repos/yum/centos-qemu-ev-release-el7/base + check_yum_sync_needed centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-qemu-ev-release-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-qemu-ev-release-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-qemu-ev-release-el7/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/glusterfs-5-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/glusterfs-5-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 9267118 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 9267118 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" 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-ansible-hosted-engine-setup/commit/9267118f4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3823/

2 1

[CQ]: 9267118 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 9267118 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" 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-ansible-hosted-engine-setup/commit/9267118f4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12637/

2 1

[CQ]: 97013,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97013,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97013/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12635/

2 1

[CQ]: 97474, 2 (ovirt-engine-wildfly) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97474,2 (ovirt-engine-wildfly) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97474/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12633/

2 1

[CQ]: 97498, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97498,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://gerrit.ovirt.org/#/c/97498/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3821/

2 1

[CQ]: 97498, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Feb '19

04 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97498,1 (ovirt-engine-nodejs-modules) failed. However, this change seems not to be the root cause for this failure. Change 97491,3 (ovirt-engine-nodejs- modules) 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 97491,3 (ovirt-engine-nodejs- modules) 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/97498/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97491/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12631/

2 1

[CQ]: 97481,1 (vcredist-x86) failed "ovirt-master" system tests
by oVirt Jenkins 04 Feb '19

04 Feb '19

Change 97481,1 (vcredist-x86) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97481/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12627/

2 1

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 04 Feb '19

04 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2666: ---------------------------------- This has to do with centos repos as the needed package was not in the correct centos repo. We are running the fix's now > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 04 Feb '19

04 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2666: ----------------------------- Labels: ost_failures ost_packages (was: ) > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 04 Feb '19

04 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2666: ---------------------------------- thanks Nir, there is a packaging issue. I will take a look. Cheers, Dafna On Sun, Feb 3, 2019 at 8:19 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, Feb 3, 2019 at 8:17 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, Feb 3, 2019 at 7:27 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> I had 2 OST failure today with the same infrastructure failure, before >>> running any test: >>> >>> + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' >>> + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp >>> ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' >>> otopi-debug-plugins cronie >>> Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 >>> (alocalsync) >>> Requires: device-mapper = 7:1.02.149-10.el7_6.3 >>> Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 >>> (installed) >>> device-mapper = 7:1.02.149-10.el7_6.2 >>> ret=1 >>> + echo 'install failed with status 1' >>> + exit 1 >>> - STDERR >>> >>> Links to failed builds: >>> - >>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… >>> - >>> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… >>> >>> The last successful build was at Feb 1: >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ >>> >>> The trend show that all builds failed since Feb 3 9:02 am. >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend >>> >> >> I started another build from master + doc patch (no code change) >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4012/ >> > > Fail with the same issue. > > >> >> >>> This issue is blocking 4.3 work on 4k support. >>> >>> Nir >>> >>> >>> > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Nir Soffer 04 Feb '19

04 Feb '19

I had 2 OST failure today with the same infrastructure failure, before running any test: + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 (alocalsync) Requires: device-mapper = 7:1.02.149-10.el7_6.3 Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) device-mapper = 7:1.02.149-10.el7_6.2 ret=1 + echo 'install failed with status 1' + exit 1 - STDERR Links to failed builds: - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… The last successful build was at Feb 1: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ The trend show that all builds failed since Feb 3 9:02 am. https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend This issue is blocking 4.3 work on 4k support. Nir

2 3

Fwd: ** PROBLEM Service Alert: ovirt-mirrorchecker/ftp.snt.utwente.nl/pub/software/ovirt mirror site last sync is CRITICAL **
by Ehud Yonasi 04 Feb '19

04 Feb '19

Hey, Could you please check the status with the ovirt mirror? Thanks in advance! ---------- Forwarded message --------- From: <nagios(a)monitoring.ovirt.org> Date: Mon, Feb 4, 2019 at 10:48 AM Subject: ** PROBLEM Service Alert: ovirt-mirrorchecker/ ftp.snt.utwente.nl/pub/software/ovirt mirror site last sync is CRITICAL ** To: <eyonasi(a)redhat.com> ***** Nagios ***** Notification Type: PROBLEM Service: ftp.snt.utwente.nl/pub/software/ovirt mirror site last sync Host: ovirt-mirrorchecker Address: web-ovirt-mirrorchecker.apps.ovirt.org State: CRITICAL Date/Time: Mon Feb 4 08:48:12 UTC 2019 Additional Info: CRITICAL - 4166860 seconds since last sync, which are 1157.4611 hours.

1 0

master snapshot repo is empty (was: Re: failed engine check_patch)
by Yedidyah Bar David 04 Feb '19

04 Feb '19

On Sun, Feb 3, 2019 at 2:27 PM Eitan Raviv <eraviv(a)redhat.com> wrote: > > hi Didi, > I have several failing patches on the following: > https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/47… > https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/47… > https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/47… > any idea? > thanks > > 11:57:15 ============================= test session starts ============================== > 11:57:15 platform linux2 -- Python 2.7.5 -- py-1.4.32 -- pytest-2.7.0 > 11:57:15 rootdir: /home/jenkins/workspace/ovirt-engine_master_check-patch-el7-x86_64/ovirt-engine/packaging/setup, inifile: > 11:57:16 collected 0 items / 1 errors > 11:57:16 > 11:57:16 ==================================== ERRORS ==================================== > 11:57:16 ___ ERROR collecting tests/ovirt_engine_setup/engine_common/test_database.py ___ > 11:57:16 packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py:19: in <module> > 11:57:16 import ovirt_engine_setup.engine_common.database as under_test # isort:skip # noqa: E402 > 11:57:16 packaging/setup/ovirt_engine_setup/engine_common/database.py:29: in <module> > 11:57:16 from otopi import base > 11:57:16 E ImportError: No module named otopi > 11:57:16 =========================== 1 error in 0.44 seconds ============================ > > https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ is empty. Adding infra. -- Didi

3 7

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #256
by jenkins＠jenkins.phx.ovirt.org 04 Feb '19

04 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 2475ed85fd8420315ce9833bd51cc956f7bda7e8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2475ed85fd8420315ce9833bd51cc956f7bda7e8 Commit message: "vcredist-x86: move to oVirt stdci v2" > git rev-list --no-walk 2475ed85fd8420315ce9833bd51cc956f7bda7e8 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins2839031003625581779.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

Jenkins build became unstable: ovirt_4.3_publish-rpms_nightly #17
by jenkins＠jenkins.phx.ovirt.org 04 Feb '19

04 Feb '19

See <http://jenkins.ovirt.org/job/ovirt_4.3_publish-rpms_nightly/17/display/redi…>

1 1

oVirt infra daily report - unstable production jobs - 725
by jenkins＠jenkins.phx.ovirt.org 04 Feb '19

04 Feb '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/725//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Nir Soffer (oVirt JIRA) 03 Feb '19

03 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2666: ----------------------------------- On Sun, Feb 3, 2019 at 8:17 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, Feb 3, 2019 at 7:27 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> I had 2 OST failure today with the same infrastructure failure, before >> running any test: >> >> + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' >> + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp >> ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' >> otopi-debug-plugins cronie >> Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 >> (alocalsync) >> Requires: device-mapper = 7:1.02.149-10.el7_6.3 >> Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 >> (installed) >> device-mapper = 7:1.02.149-10.el7_6.2 >> ret=1 >> + echo 'install failed with status 1' >> + exit 1 >> - STDERR >> >> Links to failed builds: >> - >> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… >> - >> https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… >> >> The last successful build was at Feb 1: >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ >> >> The trend show that all builds failed since Feb 3 9:02 am. >> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend >> > > I started another build from master + doc patch (no code change) > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4012/ > Fail with the same issue. > > >> This issue is blocking 4.3 work on 4k support. >> >> Nir >> >> >> > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Nir Soffer (oVirt JIRA) 03 Feb '19

03 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2666: ----------------------------------- On Sun, Feb 3, 2019 at 7:27 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I had 2 OST failure today with the same infrastructure failure, before > running any test: > > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 > (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > I started another build from master + doc patch (no code change) https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4012/ > This issue is blocking 4.3 work on 4k support. > > Nir > > > > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Nir Soffer (oVirt JIRA) 03 Feb '19

03 Feb '19

Nir Soffer created OVIRT-2666: --------------------------------- Summary: OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 Key: OVIRT-2666 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I had 2 OST failure today with the same infrastructure failure, before running any test: + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 (alocalsync) Requires: device-mapper = 7:1.02.149-10.el7_6.3 Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) device-mapper = 7:1.02.149-10.el7_6.2 ret=1 + echo 'install failed with status 1' + exit 1 - STDERR Links to failed builds: - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… The last successful build was at Feb 1: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ The trend show that all builds failed since Feb 3 9:02 am. https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend This issue is blocking 4.3 work on 4k support. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc27-x86_64 #1320
by jenkins＠jenkins.phx.ovirt.org 03 Feb '19

03 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 2475ed85fd8420315ce9833bd51cc956f7bda7e8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2475ed85fd8420315ce9833bd51cc956f7bda7e8 Commit message: "vcredist-x86: move to oVirt stdci v2" > git rev-list --no-walk 2475ed85fd8420315ce9833bd51cc956f7bda7e8 # timeout=10 [system-sync_mirrors-fedora-updates-fc27-x86_64] $ /bin/bash -xe /tmp/jenkins7644020306614954651.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc27 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc27 yum + local repo_name=fedora-updates-fc27 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc27 /var/www/html/repos/yum/fedora-updates-fc27/base + check_yum_sync_needed fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc27 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc27 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc27 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc27 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc27/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc27. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #493
by jenkins＠jenkins.phx.ovirt.org 03 Feb '19

03 Feb '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/493/display/red…>

1 2

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #1245
by jenkins＠jenkins.phx.ovirt.org 03 Feb '19

03 Feb '19

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/1245/display…>

1 3

u/s errors during update
by Roni Eliezer 03 Feb '19

03 Feb '19

Hi I got the following errors (see below) when I try to upgrade 4.3 u/s Any idea? --> Finished Dependency Resolution Error: Package: 1:openvswitch-2.10.1-1.el7.x86_64 (@centos-ovirt43-testing) Requires: librte_efd.so.1()(64bit) Removing: dpdk-17.11-15.el7.x86_64 (@rhel-extras) librte_efd.so.1()(64bit) Updated By: dpdk-18.11-2.el7_6.x86_64 (rhel-extras) Not found Available: dpdk-17.11-7.el7.x86_64 (rhel-extras) librte_efd.so.1()(64bit) Available: dpdk-17.11-11.el7.x86_64 (rhel-extras) librte_efd.so.1()(64bit) Available: dpdk-17.11-13.el7.x86_64 (rhel-extras) librte_efd.so.1()(64bit) Available: dpdk-2.0.0-8.el7.x86_64 (rhel-extras) Not found Available: dpdk-2.2.0-2.el7.x86_64 (rhel-extras) Not found Available: dpdk-2.2.0-3.el7.x86_64 (rhel-extras) Not found Available: dpdk-16.11.2-4.el7.x86_64 (rhel-extras) Not found Error: Package: 1:openvswitch-ovn-common-2.10.1-1.el7.x86_64 (@centos-ovirt43-testing) Requires: librte_pmd_softnic.so.1()(64bit) Removing: dpdk-17.11-15.el7.x86_64 (@rhel-extras) librte_pmd_softnic.so.1()(64bit) Updated By: dpdk-18.11-2.el7_6.x86_64 (rhel-extras) Not found Available: dpdk-17.11-7.el7.x86_64 (rhel-extras) librte_pmd_softnic.so.1()(64bit) Available: dpdk-17.11-11.el7.x86_64 (rhel-extras) librte_pmd_softnic.so.1()(64bit) Available: dpdk-17.11-13.el7.x86_64 (rhel-extras) librte_pmd_softnic.so.1()(64bit) Available: dpdk-2.0.0-8.el7.x86_64 (rhel-extras) Not found Available: dpdk-2.2.0-2.el7.x86_64 (rhel-extras) Not found Available: dpdk-2.2.0-3.el7.x86_64 (rhel-extras) Not found Available: dpdk-16.11.2-4.el7.x86_64 (rhel-extras) Not found

1 0

oVirt infra daily report - unstable production jobs - 724
by jenkins＠jenkins.phx.ovirt.org 03 Feb '19

03 Feb '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/724//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2160
by jenkins＠jenkins.phx.ovirt.org 02 Feb '19

02 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins153593319555036193.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #251
by jenkins＠jenkins.phx.ovirt.org 02 Feb '19

02 Feb '19

1 1

oVirt infra daily report - unstable production jobs - 723
by jenkins＠jenkins.phx.ovirt.org 02 Feb '19

02 Feb '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/723//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97491, 3 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '19

01 Feb '19

Change 97491,3 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-master" 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://gerrit.ovirt.org/#/c/97491/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12629/

1 0

[Ovirt] [CQ weekly status] [01-02-2019]
by Dafna Ron 01 Feb '19

01 Feb '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#2) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine-setup due to build-artiacts job on Jan 25. the issue is worked on by Simon Tiraboschi *CQ-Master:* GREEN (#1) There are no current issues in master CQ During the week we had 3 regressions for ovirt-engine 1. Domain version 5 feature was merged but its was not yet supported on vdsm side: https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 24-01-2019 test failing: 002_bootstrap.add_master_storage_domain Fix: https://gerrit.ovirt.org/#/c/97262/ - storage: Make default domain verion V4 for 4.3 2. CQ was still failing on create domain v5 after the fix was merged to fix regression #1 https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 26-01-2019 test failing: 002_bootstrap.add_secondary_storage_domains Fix: https://gerrit.ovirt.org/#/c/97408/ - storage: V5 is not a latest domain version yet ** first patch fixed the domain create for manual create but via the API the version was available which is why we were still failing on CQ. 3. Added callbacks for MBS disks causing regular disks to use callbacks unnecessarily https://gerrit.ovirt.org/#/c/96815/ - core: set VmDevices properly when creating and attaching We saw this regression once #1 and #2 regressions were fixed. Date first failure detected: 30-01-2019 Fix: https://gerrit.ovirt.org/#/c/97428/ - core: partial revert of 4d439006 Ovirt-engine passed on 31-01-2019 Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0