- Infra - oVirt List Archives

[CQ]: 97677,7 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 19 Feb '19

19 Feb '19

Change 97677,7 (ovirt-engine-sdk) 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/97677/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13009/

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

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

1 0

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

19 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/740//artifact/exported-a… Cheers, Jenkins

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3643 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-052rf.

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97821, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[vdsm]jenkins build on demand doesn't seem to work on stable branch
by Francesco Romani 18 Feb '19

18 Feb '19

Hi Infra, I'd like to build RPMs using "ci please build" for my https://gerrit.ovirt.org/#/c/97737/ - the ultimate goal is to have OST validate my patch. It seems to me that the "ci please build" command isn't working, or at least I can't see any feedback about it. Is this automation still enabeld for the stable branch? Any idea what's going on? Thanks, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

2 2

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

18 Feb '19

Failed to run project_setup.sh for: #3635 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-h0snq.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3635 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-h540s.

1 0

[CQ]: 97820, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

After import storage many of my vm's disks not appear
by Kalil de A. Carvalho 18 Feb '19

18 Feb '19

Hello all. It is been a while that I used the oVirt and on the same time, the company where I started to work, has a big problem with the engine, we lose it. We did not have any backup. To try recovery the enverioment I installed a knew oVirt, this time Hosted Engine, and import the Storage. I could import and start some vm's but the most part not appear for me, dosen't show on "Disk Import", "VM Import" and any place. I know that is there, because show me that size. May I see, like list, this disks? I can't do this throught oVirt web. Is there any way to bring dist disks back? I already search this tasks but with no luck. oVirt ver: 4.2.8.2-1.el7 Any one can help, please? Best regards. -- Atenciosamente, Kalil de A. Carvalho

2 1

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

18 Feb '19

Failed to run project_setup.sh for: #3634 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-40p3c.

1 0

[CQ]: 96986, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 4d1eb83 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (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 52f05b8 (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/4d1eb83a0… 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/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12976/

1 0

[CQ]: 07c7fd2 (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 07c7fd2 (ovirt-web-ui) 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-web-ui/commit/07c7fd24e2ae3d824a60a6951ceb97… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3899/

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3631 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-v40m2.

1 0

[CQ]: 97819,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97819,1 (ovirt-host) 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/97819/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12972/

1 0

[CQ]: 96984, 18 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3629 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-qlwpj.

1 0

[CQ]: 96980, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 7f83b03 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (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 52f05b8 (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/7f83b03f8… 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/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12960/

1 0

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

18 Feb '19

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

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #1326 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-6tqnq.

1 0

[CQ]: 97257, 24 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3625 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-xffw9.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3625 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-g2dqn.

1 0

[CQ]: 97740, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 Feb '19

Change 52f05b8 (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/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12945/

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3623 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-r7jq7.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3623 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-3tvx6.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3623 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-t2zm6.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3621 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-td12m.

1 0

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

18 Feb '19

Failed to run project_setup.sh for: #3621 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-rp2sn.

1 0

[CQ]: 97270, 24 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97379, 20 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97764, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97764,2 (ovirt-engine-api-model) 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/97764/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12940/

1 0

[CQ]: 97800, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 97765, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

Best Practice to Deploy HostedEngine oVirt Environment
by Mohd Hanief Harun 18 Feb '19

18 Feb '19

Hi all, Im new in rhv and oVirt, hope there some space for the noob question :) Let say I have 2 hypervisors and 1 storage server. Where is the best practice to install self-hosted engine? In hypervisors or storage? I have experienced installing self-hosted engine in 2 storages. If something happened to the storage 1, ovirt-engine (ovirt-manager) will automatically migrate to storage 2. But this time is difference. We only have 1 storage. my concern is, if something happened to the storage, I cannot access my ovirt-manager. I'm thinking to deploy self-hosted engine in hypervisors since we have 2 hypervisors. any advise? what is the best practice? If you have any tutorial installing hosted engine in 2 hypervisors would be very appreciate. thanks.

2 1

[CQ]: 66932, 31 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

[CQ]: 7d67266 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 7d67266 (ovirt-web-ui) 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-web-ui/commit/7d6726676871274417e78139507a96… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12934/

1 0

[CQ]: 96836, 27 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

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

1 0

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

18 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/739//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96835, 27 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

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

1 0

[CQ]: 96829, 28 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Feb '19

17 Feb '19

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

1 0

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

17 Feb '19

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

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 17-02-2019 ] [ 001_initialize_engine.test_initialize_engine ]
by Dafna Ron 17 Feb '19

17 Feb '19

Hi, we are failing upgrade from release suite on ovirt-engine master. CQ points below patch as root cause: https://gerrit.ovirt.org/#/c/97719/ - webadmin: don't allow trimming whitespace for the kernel cmdline Unfortunately the process logs are not collected and I have no way of seeing why the processes failed. I can try to debug this further in the morning ERROR: setup log: 2019-02-17 10:17:24,507-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stderr: Job for rh-postgresql95-postgresql.service failed because the control process exited with error code. See "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" for details. 2019-02-17 10:17:24,508-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'File transaction for '/var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf'' 2019-02-17 10:17:24,509-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 201, in _misc self._provisioning.provision() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 498, in provision self.restartPG() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 399, in restartPG state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'rh-postgresql95-postgresql' 2019-02-17 10:17:24,511-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Failed to start service 'rh-postgresql95-postgresql' 2019-02-17 10:17:24,556-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe 0: 0 0.0.0.0:111 0.0.0.0:0 LISTEN 4191 /usr/sbin/rpcbind 1: 29 0.0.0.0:662 0.0.0.0:0 LISTEN 4225 /usr/sbin/rpc.statd 2: 0 0.0.0.0:22 0.0.0.0:0 LISTEN 3361 /usr/sbin/sshd 3: 0 0.0.0.0:892 0.0.0.0:0 LISTEN 4266 /usr/sbin/rpc.mountd 4: 0 0.0.0.0:2049 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 5: 0 0.0.0.0:32803 0.0.0.0:0 LISTEN UnknownPID UnknownEXE 6: 0 192.168.201.2:22 192.168.201.1:54800 ESTABLISHED 8189 /usr/sbin/sshd 2019-02-17 10:17:24,557-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2019-02-17 10:17:24,558-0500 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback Loaded plugins: fastestmirror, versionlock

2 4

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

17 Feb '19

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

1 0