- Infra - oVirt List Archives

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

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

1 0

[CQ]: 98143,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 02 Mar '19

02 Mar '19

Change 98143,2 (vdsm) 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/98143/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13214/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 02 Mar '19

02 Mar '19

Failed to run project_setup.sh for: #1464 containerized-data-importer [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-nc8fm.

1 0

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

02 Mar '19

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

1 0

[JIRA] (OVIRT-2690) v2v_conversion_host jenkins job bugged
by Eyal Edri (oVirt JIRA) 02 Mar '19

02 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2690?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2690: ---------------------------------- This is probably due to the project rename in GitHub ( dropping the ovirt prefix ). The RPM names are not set by CI, its building according to the scripts under the GitHub repo - https://github.com/oVirt/v2v-conversion-host/blob/master/v2v-conversion-hos… Adding the maintainers, it probably needs a fix on the repo itself. ( if not it might be a bug in STD-CI due to the repo change, adding also Barak and Daniel to check ) We can help with cleaning up the repos after the project owner fix the naming in the project itself. On Fri, Mar 1, 2019 at 7:19 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > Hi, > just noticed today we have a jenkins job: > https://jenkins.ovirt.org/job/oVirt_v2v-conversion-host_standard-on-ghpush/… > > which generates packages named like: > > > v2v-conversion-host-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.src.rpm > v2v-conversion-host-1.11.0.tar.gz > > v2v-conversion-host-ansible-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > > v2v-conversion-host-debugsource-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > > v2v-conversion-host-provider-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > > v2v-conversion-host-provider-debuginfo-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > > v2v-conversion-host-wrapper-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > > which are breaking NVR naming conventions for RPMs and are probably the > result of a bug within jenkins job. > > Please fix the job as soon as possible and clean up > - https://resources.ovirt.org/repos/ovirt/tested/master > - https://resources.ovirt.org/repos/ovirt/tested/4.2 > - https://resources.ovirt.org/pub/ovirt-4.2-snapshot > - https://resources.ovirt.org/pub/ovirt-master-snapshot > > Thanks, > > -- > > SANDRO BONAZZOLA > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://red.ht/sig> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3T43P5W7BKI2C… > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > v2v_conversion_host jenkins job bugged > -------------------------------------- > > Key: OVIRT-2690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2690 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > just noticed today we have a jenkins job: > https://jenkins.ovirt.org/job/oVirt_v2v-conversion-host_standard-on-ghpush/… > which generates packages named like: > v2v-conversion-host-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.src.rpm > v2v-conversion-host-1.11.0.tar.gz > v2v-conversion-host-ansible-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > v2v-conversion-host-debugsource-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-provider-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-provider-debuginfo-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm > v2v-conversion-host-wrapper-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm > which are breaking NVR naming conventions for RPMs and are probably the > result of a bug within jenkins job. > Please fix the job as soon as possible and clean up > - https://resources.ovirt.org/repos/ovirt/tested/master > - https://resources.ovirt.org/repos/ovirt/tested/4.2 > - https://resources.ovirt.org/pub/ovirt-4.2-snapshot > - https://resources.ovirt.org/pub/ovirt-master-snapshot > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1462 containerized-data-importer [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-bw800.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1462 containerized-data-importer [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-5lwdh.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1461 containerized-data-importer [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-bsw0f.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1461 containerized-data-importer [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-63r6n.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1459 containerized-data-importer [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-56n01.

1 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1458 containerized-data-importer [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-gwkk8.

1 0

[CQ]: 95870,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 01 Mar '19

01 Mar '19

Change 95870,6 (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/95870/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13208/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1457 containerized-data-importer [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-f5gss.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1457 containerized-data-importer [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-68zmd.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1453 containerized-data-importer [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-cq769.

1 0

[JIRA] (OVIRT-2690) v2v_conversion_host jenkins job bugged
by sbonazzo (oVirt JIRA) 01 Mar '19

01 Mar '19

sbonazzo created OVIRT-2690: ------------------------------- Summary: v2v_conversion_host jenkins job bugged Key: OVIRT-2690 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2690 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, just noticed today we have a jenkins job: https://jenkins.ovirt.org/job/oVirt_v2v-conversion-host_standard-on-ghpush/… which generates packages named like: v2v-conversion-host-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.src.rpm v2v-conversion-host-1.11.0.tar.gz v2v-conversion-host-ansible-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm v2v-conversion-host-debugsource-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm v2v-conversion-host-provider-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm v2v-conversion-host-provider-debuginfo-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.x86_64.rpm v2v-conversion-host-wrapper-1.11.0-0.oVirt_v2v_conversion_host_standard_on.githpush_13.20190301133957.fc27.noarch.rpm which are breaking NVR naming conventions for RPMs and are probably the result of a bug within jenkins job. Please fix the job as soon as possible and clean up - https://resources.ovirt.org/repos/ovirt/tested/master - https://resources.ovirt.org/repos/ovirt/tested/4.2 - https://resources.ovirt.org/pub/ovirt-4.2-snapshot - https://resources.ovirt.org/pub/ovirt-master-snapshot Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[RHV] [CQ weekly status] [01-03-2019]
by Dafna Ron 01 Mar '19

01 Mar '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-RHV-4.2:* GREEN (#1) Last failure was on 28-02-2019 for project rhevm-appliance due to a failed build-artifacts job. this issue is still happening and message was sent to developer. *CQ-RHV-Master:* GREEN (#1) Last failure is identical to 4.2 - build-artifacts for the same project. ** We do not yet have a 4.3 CQ job which we will start working on next week. Current running jobs for 4.2 [1] and for master [2] can be found below: [1] https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Change%20qu… [2] https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Change%20qu… 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)

1 0

[Ovirt] [CQ weekly status] [01-03-2019]
by Dafna Ron 01 Mar '19

01 Mar '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 (#1) Last CQ job failure on 4.2 was 27-02-2019 on project ovirt-provider-ovn due to a failed build-artifacts job. this issue is now fixed. Please note that this is a CQ job failure but not an OST job failure as we exit if no package is available. *CQ-4.3*: RED (#1) We added a CQ job for 4.3 but not all projects created the branch yet. I created a google sheet to follow the advancement of this work and I will use this report to ask all the managers to go over the doc and add info: https://docs.google.com/spreadsheets/d/1i142cTN_0QwOvogtlQiF6bcIYxTpBqYBed2… *CQ-Master:* RED (#1) We have sporadic failures in test get_host_devices this is effecting all projects and we have yet to know what is causing the issue. Michal checked the issue and thinks the test should be modified to do a re-try as the info is filled by the host 4 seconds after the query is sent. Milan was asked to add a loop with 1s delay to get_host_devices to fix the test. Please note that we have ruled out a possible infra cause for this failure before alerting dev as the failure is sporadic and happens on multiple projects. Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2686 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

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1448 containerized-data-importer [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-jbwbg.

1 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1448 containerized-data-importer [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-gh7m8.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1447 containerized-data-importer [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-htc0w.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1447 containerized-data-importer [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-m0tk1.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1444 containerized-data-importer [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-dvrfl.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1444 containerized-data-importer [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-8f949.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #1442 containerized-data-importer [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-q1l85.

1 1

[NOTICE] infra issue in progress in jenkins
by Dafna Ron 01 Mar '19

01 Mar '19

Hi, We had a job fail due to a failure in yum. it seems yum is searching for repodata in a wrong location. Evgheni is currently working to investigate and fix the problem and will update soon Jira opened: https://ovirt-jira.atlassian.net/browse/OVIRT-2689 Thanks, Dafna

1 1

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #3390 vdsm [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 vm0036.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #3387 vdsm [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 vm0042.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #3391 vdsm [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 vm0037.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2689) Failing to run jobs with due to yum failure
by Evgheni Dereveanchin (oVirt JIRA) 01 Mar '19

01 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2689?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2689: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Failing to run jobs with due to yum failure > ------------------------------------------- > > Key: OVIRT-2689 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2689 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Priority: Highest > > I failed a check-patch job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… > Evgheni checked and he says we have an on-going issue in which yum is searching for repodata in wrong location. > This will most likely cause more jobs to fail. > Evgheni is working on finding a fix and then investigating this issue and what caused it -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2689) Failing to run jobs with due to yum failure
by Dafna Ron (oVirt JIRA) 01 Mar '19

01 Mar '19

Dafna Ron created OVIRT-2689: -------------------------------- Summary: Failing to run jobs with due to yum failure Key: OVIRT-2689 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2689 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Dafna Ron Assignee: infra Priority: Highest I failed a check-patch job: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… Evgheni checked and he says we have an on-going issue in which yum is searching for repodata in wrong location. This will most likely cause more jobs to fail. Evgheni is working on finding a fix and then investigating this issue and what caused it -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Failed to run project_setup.sh for: #3368 vdsm [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 vm0037.workers-phx.ovirt.org.

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 496 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/496/ Build Number: 496 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #496 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.resize_and_refresh_storage_domain_42 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running 59628f54 on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev lago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine output: Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents). Logical volume vg1_storage/lun0_bdev successfully resized. lago.ssh: DEBUG: start task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running 59c76e60 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt lago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine output: 360014052b36c080242849af94e08d593 3600140577ca2fe2129b46cfadb969690 3600140582c361006901472d903755e3c 36001405e4f3abc5714e4d42929c9534b 36001405ec963d2b05d748c4bb4ba46f6 --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 527, in resize_and_refresh_storage_domain logical_units=luns File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/__init__.py", line 264, in TestEvent lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:cad32885-9201-470b-8ec9-53ade3f2e147:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running 59628f54 on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev\nlago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command 59628f54 on lago-compat-4-2-suite-master-engine output:\n Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents).\n Logical volume vg1_storage/lun0_bdev successfully resized.\n\nlago.ssh: DEBUG: start task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:c433966f-7e18-4d1e-a68d-218bfda20420:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running 59c76e60 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt\nlago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command 59c76e60 on lago-compat-4-2-suite-master-engine output:\n 360014052b36c080242849af94e08d593\n3600140577ca2fe2129b46cfadb969690\n3600140582c361006901472d903755e3c\n36001405e4f3abc5714e4d42929c9534b\n36001405ec963d2b05d748c4bb4ba46f6\n\n--------------------- >> end captured logging << ---------------------'

1 3

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 498 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/498/ Build Number: 498 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #498 [Milan Zamazal] Add upgrade-from-release_suite-4.3 [Gal Ben Haim] global-setup: Collect more info about docker [Barak Korren] slaves_deploy: Fix STDCI slave settings ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_41 Error Message: Could not find block_vda_1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda_1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda_1 device in host devices:

1 1

[CQ]: 98126,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 01 Mar '19

01 Mar '19

Change 98126,3 (vdsm) 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/98126/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13194/

1 0

oVirt infra daily report - unstable production jobs - 750
by jenkins＠jenkins.phx.ovirt.org 01 Mar '19

01 Mar '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/750//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98058, 4 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

Change 98058,4 (ovirt-provider-ovn) 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/98058/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13192/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1437 containerized-data-importer [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-7gf81.

1 1

[CQ]: 96485,6 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

Change 96485,6 (ovirt-imageio) 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/96485/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13187/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1437 containerized-data-importer [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-srt89.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1436 containerized-data-importer [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-p1nn5.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1435 containerized-data-importer [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-thpcq.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1433 containerized-data-importer [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-hkn5s.

1 1

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '19

Failed to run project_setup.sh for: #1432 containerized-data-importer [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-x502z.

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-02-2019 ] [ 002_bootstrap.resize_and_refresh_storage_domain ]
by Dafna Ron 28 Feb '19

28 Feb '19

Hi, The test failed due to not finding master storage domain I am seeing a build of engine that passed so its possible that this is related to the random failures we have been having on other tests but since the change reported is storage related, can you please review the logs to see if anything happened to the master domain while trying to resize? CQ reported this change as root cause: https://gerrit.ovirt.org/#/c/98015/6 - blockSD: Move legacy block size constants to sd build failure: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13175/ logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13175/artifa… errors in log: 2019-02-27 17:35:02,222-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM la go-basic-suite-master-host-1 command ConnectStoragePoolVDS failed: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' 2019-02-27 17:35:02,222-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker. ConnectStoragePoolVDSCommand' return value 'StatusOnlyReturn [status=Status [code=304, message=Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5 a9']]' 2019-02-27 17:35:02,222-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] HostName = lago-basic-suite-master-host-1 2019-02-27 17:35:02,223-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Command 'ConnectStoragePoolVDSCommand(HostName = lago-basic-suite-master-host-1, ConnectStoragePoolVDSCommandParameters:{hostId='1ac0eda2-0980-40df-b029-b262680696a4', vdsId='1ac0eda2-0980-40df-b029-b262680696a4', storagePoolId='1c79b83e-32d6-43e0-bc61-2955e42c3a58', masterVersion='1'})' execution failed: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' 2019-02-27 17:35:02,223-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (EE-ManagedThreadFactory-engine-Thread-23) [558e4473] Exception: org.ovirt.engine.core.vdsbroker.irsbroker.IRSNoMasterDomainException: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: u'spUUID=1c79b83e-32d6-43e0-bc61-2955e42c3a58, msdUUID=7a7e1d7b-08aa-49f6-bdf2-4be64260b5a9' at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:50) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.proceedConnectProxyReturnValue(ConnectStoragePoolVDSCommand.java:48) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.proceedProxyReturnValue(ConnectStoragePoolVDSCommand.java:36) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand.executeVdsBrokerCommand(ConnectStoragePoolVDSCommand.java:32) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:396) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) [:1.8.0_191] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_191] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_191] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.bll.storage.pool.RefreshPoolSingleAsyncOperation.execute(RefreshPoolSingleAsyncOperation.java:59) [bll.jar:] at org.ovirt.engine.core.utils.SynchronizeNumberOfAsyncOperations$AsyncOpThread.call(SynchronizeNumberOfAsyncOperations.java:43) [utils.jar:] at org.ovirt.engine.core.utils.SynchronizeNumberOfAsyncOperations$AsyncOpThread.call(SynchronizeNumberOfAsyncOperations.java:32) [utils.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalCallable.call(ThreadPoolUtil.java:117) [utils.jar:] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:]

2 2

[CQ]: 98063, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

Change 98063,2 (ovirt-provider-ovn) 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/98063/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13180/

1 0

[ANN] oVirt 4.3.1 is now generally available
by Sandro Bonazzola 28 Feb '19

28 Feb '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.1, as of February 26th, 2019. This update is the first in a series of stabilization updates to the 4.3 series. 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. Notes: - oVirt Appliance is available for EL7 only - oVirt Node is available for EL7 only [2] - Fedora 28 based appliance and node couldn't be built due to a bug in Lorax (the tool used to build the images) affecting Fedora 28 and still pending a build from Fedora project. oVirt Node has been updated including: - oVirt 4.3.1: http://www.ovirt.org/release/4.3.1/ - ansible-2.7.8: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant EPEL Errata included: - FEDORA-EPEL-2019-5f2f93029f security update in Fedora EPEL 7 for ansible ( https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5f2f93029f ) Relevant CentOS Errata included: - CESA-2019:0231 Important CentOS 7 spice Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023192.html ) - CESA-2019:0368 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023202.html ) Additional Resources: * Read more about the oVirt 4.3.1 release highlights: http://www.ovirt.org/release/4.3.1/ * 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.1/ [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]: 98097, 1 (ovirt-release) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Feb '19

28 Feb '19

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

1 0

[CQ]: 98099, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Feb '19

28 Feb '19

A system test invoked by the "ovirt-4.3" change queue including change 98099,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) 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 97519,2 (ovirt-node-ng-image) 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/98099/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/93/

1 0