February 2019 - Infra - oVirt List Archives

[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

[CQ]: 96549, 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 96549,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/96549/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/12922/

1 0

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

17 Feb '19

Failed to run project_setup.sh for: #3616 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-2lxh8.

1 0

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

17 Feb '19

Failed to run project_setup.sh for: #3615 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-90rnw.

1 0

[JIRA] (OVIRT-2681) please move ovirt-openshift-extensions to container based slaves
by Roy Golan (oVirt JIRA) 17 Feb '19

17 Feb '19

Roy Golan created OVIRT-2681: -------------------------------- Summary: please move ovirt-openshift-extensions to container based slaves Key: OVIRT-2681 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2681 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra I'd like to use multi-stage container builds, please adjust ovirt/ovirt-openshift-extensions project accordingly. Thanks, Roy -- 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 17 Feb '19

17 Feb '19

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

1 0

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

17 Feb '19

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

1 0

[CQ]: 97715, 3 (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 97715,3 (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/97715/3 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/12920/

1 0

[JIRA] (OVIRT-2680) puppetdb on foreman.ovirt.org OOM
by Emil Natan (oVirt JIRA) 17 Feb '19

17 Feb '19

Emil Natan created OVIRT-2680: --------------------------------- Summary: puppetdb on foreman.ovirt.org OOM Key: OVIRT-2680 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2680 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Emil Natan Assignee: infra Pupperdb on forman.ovirt.org went down, it seems because of OOM. Below is the message from puppetdb-daemon.log. Not sure if this is the first time this happens, if yes then maybe just increase memory and swap. java.lang.OutOfMemoryError: Java heap space Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ... Heap dump file created [285263302 bytes in 2.953 secs] # # java.lang.OutOfMemoryError: Java heap space # -XX:OnOutOfMemoryError="kill -9 %p" # Executing /bin/sh -c "kill -9 6929"... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97769, 2 (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 97769,2 (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/97769/2 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/12918/

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 17 Feb '19

17 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1732: ------------------------------------- Its not done. You can see changes piling up every time checp-patch starts to fail consistently in one of the downstream projects. > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

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

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97705,6 (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/97705/6 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/12916/

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97693,10 (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/97693/10 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/12915/

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97602,27 (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/97602/27 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/12913/

1 0

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

16 Feb '19

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

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97759,3 (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/97759/3 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/12909/

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97781,1 (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/97781/1 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/12907/

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97780,1 (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/97780/1 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/12906/

1 0

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

16 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97776,2 (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/97776/2 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/12904/

1 0

[CQ]: 97775,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 16 Feb '19

16 Feb '19

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

1 0

[ OST Failure Report ] [ oVirt Master/4.2 (ovirt-vmconsole) ] [ 15-02-2019 ] [ TEST NAME ]
by Dafna Ron 16 Feb '19

16 Feb '19

Hi, We are failing to deploy hosts in upgrade suites on both master and 4.2 for project ovirt-vmconsole. it seems we are missing packages for selinux-policy. Root cause identified by CQ as: https://gerrit.ovirt.org/#/c/97704/ - spec: clean up and reorganize can you please take a look at this issue? Sandro requested a bug so I opened one: https://bugzilla.redhat.com/show_bug.cgi?id=1677630 Error: 019-02-14 12:11:42,063-0500 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy >= 3.13.1-229.el7_6.9', u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy-base >= 3.13.1-229.el7_6.9'] 2019-02-14 12:11:42,063-0500 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-8JzESBo7eU/pythonlib/otopi/context.py", line 132, in _executeMethod method['method']() File "/tmp/ovirt-8JzESBo7eU/otopi-plugins/otopi/packagers/yumpackager.py", line 248, in _packages self.processTransaction() File "/tmp/ovirt-8JzESBo7eU/otopi-plugins/otopi/packagers/yumpackager.py", line 262, in processTransaction if self._miniyum.buildTransaction(): File "/tmp/ovirt-8JzESBo7eU/pythonlib/otopi/miniyum.py", line 920, in buildTransaction raise yum.Errors.YumBaseError(msg) YumBaseError: [u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy >= 3.13.1-229.el7_6.9', u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy-base >= 3.13.1-229.el7_6.9'] 2019-02-14 12:11:42,064-0500 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Package installation': [u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy >= 3.13.1-229.el7_6.9', u'ovirt-vmconsole-1.0.6-3.el7.noarch requires selinux-policy-base >= 3.13.1-229.el7_6.9'] Thanks, Dafna

3 8

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

16 Feb '19

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

1 0

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

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

1 0

[CQ]: 97792, 1 (ovirt-log-collector) failed "ovirt-master" system tests
by oVirt Jenkins 15 Feb '19

15 Feb '19

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

1 0

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

15 Feb '19

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

1 0

[JIRA] (OVIRT-1741) Get oVirt listed on https://release-monitoring.org/
by sbonazzo (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1741?page=com.atlassian.jira.… ] sbonazzo reassigned OVIRT-1741: ------------------------------- Assignee: sbonazzo (was: infra) > Get oVirt listed on https://release-monitoring.org/ > --------------------------------------------------- > > Key: OVIRT-1741 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1741 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: sbonazzo > Priority: Low > > https://release-monitoring.org/ seems to be a system that sends notification events when opens source projects release new versions. > Various systems seem to be listening and reacting on those events. > We should probably have oVirt listed there and sending events. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-497) [docs] Add documents on what's on the ci-tools repo and how it gets there
by Eyal Edri (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-497?page=com.atlassian.jira.p… ] Eyal Edri commented on OVIRT-497: --------------------------------- [~ederevea] [~amarchuk] did you check if there are special pkgs there we use or part of the CI process? This is just about adding documentation to it on infra docs > [docs] Add documents on what's on the ci-tools repo and how it gets there > ------------------------------------------------------------------------- > > Key: OVIRT-497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-497 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1767: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We mirror to github > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: Icebox, gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1766) Try out the x-docs gerit plugin
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1766?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1766: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We should open tickets that lists specific problems to solve > Try out the x-docs gerit plugin > ------------------------------- > > Key: OVIRT-1766 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1766 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: documentation, gerrit > > The x-docs plugin seems to enable Gerrit to expose markdown files from projects formatted to HTML, this can be useful as an auto-generator for project docs. > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#x-… > We might be able to use this as an '{{*.ovirt.org}}' replacement for doc URLs which currently point to GitHub or ReadTheDocs... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1741) Get oVirt listed on https://release-monitoring.org/
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1741?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1741: ---------------------------------------- [~sbonazzo(a)redhat.com] do you feel this item is useful enough? > Get oVirt listed on https://release-monitoring.org/ > --------------------------------------------------- > > Key: OVIRT-1741 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1741 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Low > > https://release-monitoring.org/ seems to be a system that sends notification events when opens source projects release new versions. > Various systems seem to be listening and reacting on those events. > We should probably have oVirt listed there and sending events. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1732: ---------------------------------------- [~dron] can you check if it is already done? > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1615: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We should open items for specific problems instead > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > Labels: Icebox > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1394?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1394: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Abandoned > Remove STD-CI cleanup function cleanup_var > ------------------------------------------ > > Key: OVIRT-1394 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Gil Shinar > Assignee: infra > > We do not remember why /var/tmp is being cleaned on each STD-CI job. > /var/tmp is good place for caching stuff (maven for example). > I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1333: ---------------------------------------- [~bkorren(a)redhat.com] is this already done? > Exclude game/desktop packages from mirrors > ------------------------------------------ > > Key: OVIRT-1333 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Labels: Icebox, first_time_task > > Our mirrors currently contain full copies of the CentOS and Fedora repos, including many large game and desktop productivity packages. > We should probably clean these packages from the repos to save space and bandwidth. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-1318: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > configure backup of status.ovirt.org > ------------------------------------ > > Key: OVIRT-1318 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > status.ovirt.org was set up - need to investigate if it needs to be backed up or we can produce documentation to set up a new stats page in case something happens to the existing OpenShift gear. > We can use OpenShift's built in backup/restore functionality: > https://developers.openshift.com/managing-your-applications/backing-up-appl… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97786, 1 (ovirt-vmconsole) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Feb '19

15 Feb '19

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

1 0

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

15 Feb '19

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

1 0

[JIRA] (OVIRT-769) infra-hiera Autodeploy via Gerrit Hooks
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-769?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-769: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We plan to decommission puppet > infra-hiera Autodeploy via Gerrit Hooks > --------------------------------------- > > Key: OVIRT-769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-769 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > infra-hiera repo is already used and configured in r10k to deploy from git. > However in gerrit there is not hooks that run CI on it and that trigger > publish when it is merged to git. > Looks like it is easy to fix and we can reuse most of the hooks we have for > infra-puppet. Basically the deploy should be done using the same jenkins > job and it already does that just not triggered. > As for CI check than we need to check if puppetlint we use is sufficient. > But it might be a good start. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-768?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-768: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Decomission of MD5 Password Hashes for Infra Users > -------------------------------------------------- > > Key: OVIRT-768 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > During the work of moving password parameters from foreman to internal > hiera I noted that there are some users that still have their passwords > hashed by MD5 algorithm. > MD5 has known crypto research that make it no longer suitable for storing > passwords securely: > https://en.wikipedia.org/wiki/MD5#Security (and corresponding links). > While the hashes are stored in internal repo it is still shared and prone > to information leaks. We should ask all users to rehash their passwords > with SHA-512 and when it is done we can remove MD5 exception > in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no > longer accepted. > The current list of users left is available in infra-hiera repo. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-638) Tune Gerrit
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-638?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-638: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We will tune gerrit based on tickets listing specific problems. > Tune Gerrit > ----------- > > Key: OVIRT-638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: Low > > We should probably tune Gerrit to take proper advantage of the bigger server we now have. > This could be useful: > http://ctf-dev-environment-vagrant.s3.amazonaws.com/Gerrit-Performance-Tuni… > Few notable details: > # Most RAM on the new server is currently taken by the FS cache instead of the Gerrit Java processes. > # It seems that the Gerrit can do Git garbage collection on its own, and do so more efficiently then doing so with the Git command line. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-497) [docs] Add documents on what's on the ci-tools repo and how it gets there
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-497?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-497: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > [docs] Add documents on what's on the ci-tools repo and how it gets there > ------------------------------------------------------------------------- > > Key: OVIRT-497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-497 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

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

1 0

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

14 Feb '19

Failed to run project_setup.sh for: #3593 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-134z9.

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

[CQ]: 97767, 1 (ovirt-vmconsole) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

1 0

[CQ]: 97704,6 (ovirt-vmconsole) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #239 ovirt-provider-ovn [check-merged]. 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 vm0094.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #239 ovirt-provider-ovn [check-merged]. 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 vm0086.workers-phx.ovirt.org.

1 0

[CQ]: 97704,6 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97704,6 (ovirt-vmconsole) 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/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3875/

2 1

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

14 Feb '19

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

1 0

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

14 Feb '19

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

1 0

[CQ]: 97721,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

2 1

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

14 Feb '19

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

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2617: ----------------------------------- So think about sprint ends. Many people have PRs, they produce load. Things are already a little bit more unstable than usual, which will increase the amount of failed lanes. So people will hit "retest this please" more often ... > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2617: ----------------------------------- Well if one suspicious lane fails, we write "retest this please". This runs everything again. > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2590) Cache Docker images in the datacenter
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2590?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2590: ----------------------------------- Thinking about our CI images it can avoid peaks on the network consumption. Right now you need all of our lanes to have run on each bare-metal machine until all nodes have a cache for each image. They have up to 8gb. It is another measure to reduce the amount of failing tests because of networking issues. Setting it up should be pretty simple. The mirror needs then just to be injected before starting docker. > Cache Docker images in the datacenter > ------------------------------------- > > Key: OVIRT-2590 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2590 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roman Mohr > Assignee: infra > > What? > As a user, I expect that I don't have to care about caching to speed up > builds for the good of the CI system itself. > Right now there exists a whitelist for docker images, which will not be > remove from the build slot after the build. Instead of that I expect a > clean build environment and that in general all images which I regularly > use are cached in the cluster via e.g. a pull-through-cache [1]. > Why? > 1) Caching in a build slot is not very effective. CI runs do really-a-lot > of almost identical things in a small time-window (e.g. days). If caching > happens in the build-slot and many slots are present, then the cache > utilization will be very low. > 2) Whitelisting docker images extra for a slot where the registry runs in, > is very error prone and since it is not cached across the cluster it is > also very intransparent what the clear benefit for the user is. Especially > when thinking about scaling a CI system, that seems to leak internal > optimizations to the user. Fast builds are twice as important for the CI > system than they are for the users (by default faster and lower utilization > is always better than asking people to optimize on their side). > [1] https://docs.docker.com/registry/recipes/mirror/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97578, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

1 0

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

14 Feb '19

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

3 2

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

14 Feb '19

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

2 1

[CQ]: 97726,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

1 0

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

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

1 0

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

13 Feb '19

Hi, we are failing on project ovirt-engine in master branch on initialize engine Change suspected: https://gerrit.ovirt.org/#/c/95743/8 - core: Remove unused field VdsStatic.vdsStrength setup log is here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12864/artifa… full logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12864/artifa… Can you please check the issue? Thanks, Dafna <error> INSERT INTO gluster_config_master(config_key, config_description, minimum_supported_cluster, config_possible_values, config_feature) values('use_meta_volume', 'Meta volume for the geo-replication session', '3.5', 'false;true', 'geo_replication'); ************************** INSERT 0 1 2019-02-13 09:03:04,406-0500 Saving custom users permissions on database objects... ********* QUERY ********** copy ( select count(*) from pg_available_extensions where name = 'uuid-ossp' and installed_version IS NOT NULL ) to stdout with delimiter as '|'; ************************** 2019-02-13 09:03:04,906-0500 dbfunc_psql_die --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0000_set_version.sql ********* QUERY ********** select 4000000; ************************** 4000000 2019-02-13 09:03:05,534-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.executeRaw:863 execute-result: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'], rc=1 2019-02-13 09:03:05,534-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:921 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'] stdout: 2019-02-13 09:03:05,535-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'] stderr: FATAL: Operation aborted, found duplicate version: 04030790 2019-02-13 09:03:05,535-0500 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:435 schema.sh: FATAL: Operation aborted, found duplicate version: 04030790 2019-02-13 09:03:05,535-0500 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed 2019-02-13 09:03:05,536-0500 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Misc configuration': Engine schema refresh failed 2019-02-13 09:03:05,562-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe <error>

2 3

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

13 Feb '19

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

1 0

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

13 Feb '19

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

1 0

[CQ]: 97463,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

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

1 0

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

13 Feb '19

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

1 0

[CQ]: 97599,9 (ovirt-release) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

Change 97599,9 (ovirt-release) 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/97599/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12860/

1 0

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

13 Feb '19

Change 900b39f (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/900b39f1f… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12858/

1 0

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

13 Feb '19

Failed to run project_setup.sh for: #3562 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-7930z.

1 0

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

13 Feb '19

Change 900b39f (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/900b39f1f… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12856/

1 0

concerns about the viability of hyperkitty
by Greg Sheremeta 13 Feb '19

13 Feb '19

Hi, After a user on the users list asked about a forum, I pointed them to our hyperkitty instance [lists.ovirt.org] which people did not know about. Maybe that was a bad idea, because a few who started looking at it commented that it was broken. This is not a good community experience. [Thank you, Marc, for opening https://gitlab.com/mailman/hyperkitty/issues/206 - but no reply for 2 months on a *major* bug like that?] While investigating the threading issue today, I found a new issue (attached screenshot). Also, one person sent the same message to the list 7 times today because he never saw his message show up in the list / UI. Perhaps hyperkitty is not well-tested nor really used by others, in which case we should not use it. There are many alternative forums, including popular (although admittedly walled off) ones like reddit [ https://www.reddit.com/r/ovirt] Please share your thoughts. Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

4 7

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

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

1 0