- Infra - oVirt List Archives

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

19 Oct '18

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

1 0

[CQ]: 93922, 10 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[CQ]: 94243,5 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 18 Oct '18

18 Oct '18

Change 94243,5 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/94243/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10677/

1 0

[CQ]: 94889, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[JIRA] (OVIRT-2550) Please add maintainers to pthreading project
by Nir Soffer (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2550?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2550: ----------------------------------- On Thu, Oct 18, 2018 at 5:51 PM danken (oVirt JIRA) < Works for me, I could +2 and merge https://gerrit.ovirt.org/c/94974/. > Please add maintainers to pthreading project > -------------------------------------------- > > Key: OVIRT-2550 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2550 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > pthreading currently has no active maintainer, but has pending patches and > ci issues to solve. > Please grant admin rights to nsoffer and msobczyk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

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

18 Oct '18

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

1 0

[CQ]: 95002, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[JIRA] (OVIRT-2552) Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1
by Ehud Yonasi (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2552?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2552: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1 > ---------------------------------------------------------------------------- > > Key: OVIRT-2552 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2552 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > Priority: Low > > This is the list to remove from the yaml file the build-artifacts jobs: > job otopi_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-vmconsole_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-log-collector_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-cli_3.6_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-jdbc_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-ldap_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-misc_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-logger-log4j_4.1_build-artifacts-el7-x86_64 still exists > job vdsm-jsonrpc-java_4.1_build-artifacts-el7-x86_64 still exists > job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists > job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-engine-sdk-java_4.1_build-artifacts-el7-x86_64 still exists > job java-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-scheduler-proxy_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-optimizer_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-dashboard_4.1_build-artifacts-el7-x86_64 still exists > job ioprocess_4.1_build-artifacts-el7-x86_64 still exists > job ioprocess_4.1_build-artifacts-el7-ppc64le still exists > job vdsm_4.1_build-artifacts-el7-x86_64 still exists > job vdsm_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-hosted-engine-ha_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-hosted-engine-setup_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine_4.1_build-artifacts-el7-x86_64 still exists > job mom_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-wgt_4.1_build-artifacts-el7-x86_64 still exists > job cockpit-ovirt_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-guest-agent_4.1_build-artifacts-el6-x86_64 still exists > job ovirt-guest-agent_4.1_build-artifacts-el7-x86_64 still exists -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2552) Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1
by Ehud Yonasi (oVirt JIRA) 18 Oct '18

18 Oct '18

Ehud Yonasi created OVIRT-2552: ---------------------------------- Summary: Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1 Key: OVIRT-2552 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2552 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ehud Yonasi Assignee: infra Priority: Low This is the list to remove from the yaml file the build-artifacts jobs: job otopi_4.1_build-artifacts-el7-x86_64 still exists job ovirt-vmconsole_4.1_build-artifacts-el7-x86_64 still exists job ovirt-log-collector_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-cli_3.6_build-artifacts-el7-x86_64 still exists job ovirt-engine-extension-aaa-jdbc_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-extension-aaa-ldap_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-extension-aaa-misc_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-extension-logger-log4j_4.1_build-artifacts-el7-x86_64 still exists job vdsm-jsonrpc-java_4.1_build-artifacts-el7-x86_64 still exists job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-ppc64le still exists job ovirt-engine-sdk-java_4.1_build-artifacts-el7-x86_64 still exists job java-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists job ovirt-scheduler-proxy_4.1_build-artifacts-el7-x86_64 still exists job ovirt-optimizer_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-dashboard_4.1_build-artifacts-el7-x86_64 still exists job ioprocess_4.1_build-artifacts-el7-x86_64 still exists job ioprocess_4.1_build-artifacts-el7-ppc64le still exists job vdsm_4.1_build-artifacts-el7-x86_64 still exists job vdsm_4.1_build-artifacts-el7-ppc64le still exists job ovirt-hosted-engine-ha_4.1_build-artifacts-el7-x86_64 still exists job ovirt-hosted-engine-setup_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-sdk_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine_4.1_build-artifacts-el7-x86_64 still exists job mom_4.1_build-artifacts-el7-x86_64 still exists job ovirt-wgt_4.1_build-artifacts-el7-x86_64 still exists job cockpit-ovirt_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-x86_64 still exists job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-ppc64le still exists job ovirt-guest-agent_4.1_build-artifacts-el6-x86_64 still exists job ovirt-guest-agent_4.1_build-artifacts-el7-x86_64 still exists -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2552) Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1
by Ehud Yonasi (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2552?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2552: ------------------------------- Epic Link: OVIRT-2044 > Remove 4.1 build artifacts jobs before removing the nightly publisher of 4.1 > ---------------------------------------------------------------------------- > > Key: OVIRT-2552 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2552 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ehud Yonasi > Assignee: infra > Priority: Low > > This is the list to remove from the yaml file the build-artifacts jobs: > job otopi_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-vmconsole_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-log-collector_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-cli_3.6_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-jdbc_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-ldap_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-aaa-misc_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-extension-logger-log4j_4.1_build-artifacts-el7-x86_64 still exists > job vdsm-jsonrpc-java_4.1_build-artifacts-el7-x86_64 still exists > job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists > job python-ovirt-engine-sdk4_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-engine-sdk-java_4.1_build-artifacts-el7-x86_64 still exists > job java-ovirt-engine-sdk4_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-scheduler-proxy_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-optimizer_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-dashboard_4.1_build-artifacts-el7-x86_64 still exists > job ioprocess_4.1_build-artifacts-el7-x86_64 still exists > job ioprocess_4.1_build-artifacts-el7-ppc64le still exists > job vdsm_4.1_build-artifacts-el7-x86_64 still exists > job vdsm_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-hosted-engine-ha_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-hosted-engine-setup_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine_4.1_build-artifacts-el7-x86_64 still exists > job mom_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-wgt_4.1_build-artifacts-el7-x86_64 still exists > job cockpit-ovirt_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-x86_64 still exists > job ovirt-engine-sdk-ruby_4.1_build-artifacts-el7-ppc64le still exists > job ovirt-guest-agent_4.1_build-artifacts-el6-x86_64 still exists > job ovirt-guest-agent_4.1_build-artifacts-el7-x86_64 still exists -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 94841,7 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

2 1

[JIRA] (OVIRT-2550) Please add maintainers to pthreading project
by danken (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2550?page=com.atlassian.jira.… ] danken commented on OVIRT-2550: ------------------------------- [~nsoffer(a)redhat.com] and [~msobczyk] should answer that. > Please add maintainers to pthreading project > -------------------------------------------- > > Key: OVIRT-2550 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2550 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > pthreading currently has no active maintainer, but has pending patches and > ci issues to solve. > Please grant admin rights to nsoffer and msobczyk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 795 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Oct '18

18 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/795/ Build Number: 795 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #795 [Galit] Update the config for poll u/s sources ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-master-host-1 is in non operational state -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fd37e46a230> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 258, in _host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) RuntimeError: Host lago-hc-basic-suite-master-host-1 is in non operational state --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 228, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 275, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 258, in _host_is_up_4 raise RuntimeError('Host %s is in non operational state' % api_host.name) 'Host lago-hc-basic-suite-master-host-1 is in non operational state\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fd37e46a230>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 258, in _host_is_up_4\n raise RuntimeError(\'Host %s is in non operational state\' % api_host.name)\nRuntimeError: Host lago-hc-basic-suite-master-host-1 is in non operational state\n--------------------- >> end captured logging << ---------------------'

1 1

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

18 Oct '18

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

1 0

[JIRA] (OVIRT-2551) failure to remove journal logs
by Daniel Belenky (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2551?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2551: ------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > failure to remove journal logs > ------------------------------ > > Key: OVIRT-2551 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2551 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > Lately, we've seen an issue where systemd-journal logs dir belongs to the root group and automation (slave_cleanup.sh) fails to remove those logs and eventually fails the entire job. I can think of 2 reasons why we should remove journals: saving disk space and possibly having a clean journal for every job (though it makes debugging hard because we don't have old logs). Anyway, I think that the way we remove journal logs is improper - maybe back when David wrote this (back in 2015) it was the only way, but today we can ask journalctl to handle the logs rotation for us: > --vacuum-size=, --vacuum-time=, --vacuum-files= > Removes archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal > files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the > specified number of separate journal files remain. Note that running --vacuum-size= has only an indirect effect on the output shown by --disk-usage, as the latter includes > active journal files, while the vacuuming operation only operates on archived journal files. Similarly, --vacuum-files= might not actually reduce the number of journal files > to below the specified number, as it will not remove active journal files. --vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to > enforce any combination of a size, a time and a number of files limit on the archived journal files. Specifying any of these three parameters as zero is equivalent to not > enforcing the specific limit, and is thus redundant. > I think that we should use --vacuum-time and keep journal logs for 10-15 days. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2551) failure to remove journal logs
by Daniel Belenky (oVirt JIRA) 18 Oct '18

18 Oct '18

Daniel Belenky created OVIRT-2551: ------------------------------------- Summary: failure to remove journal logs Key: OVIRT-2551 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2551 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Lately, we've seen an issue where systemd-journal logs dir belongs to the root group and automation (slave_cleanup.sh) fails to remove those logs and eventually fails the entire job. I can think of 2 reasons why we should remove journals: saving disk space and possibly having a clean journal for every job (though it makes debugging hard because we don't have old logs). Anyway, I think that the way we remove journal logs is improper - maybe back when David wrote this (back in 2015) it was the only way, but today we can ask journalctl to handle the logs rotation for us: --vacuum-size=, --vacuum-time=, --vacuum-files= Removes archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running --vacuum-size= has only an indirect effect on the output shown by --disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly, --vacuum-files= might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files. --vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files. Specifying any of these three parameters as zero is equivalent to not enforcing the specific limit, and is thus redundant. I think that we should use --vacuum-time and keep journal logs for 10-15 days. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95011, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[JIRA] (OVIRT-2550) Please add maintainers to pthreading project
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2550?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2550: ---------------------------------- [~danken(a)redhat.com] Added. please let me know if this Jira can be closed. > Please add maintainers to pthreading project > -------------------------------------------- > > Key: OVIRT-2550 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2550 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > pthreading currently has no active maintainer, but has pending patches and > ci issues to solve. > Please grant admin rights to nsoffer and msobczyk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2549: ---------------------------------- I added dpdk to 4.2 repo as it was missing there as well which is probably what's causing the current failure. > master ovirt-engine fails on missing package > -------------------------------------------- > > Key: OVIRT-2549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2550) Please add maintainers to pthreading project
by danken (oVirt JIRA) 18 Oct '18

18 Oct '18

danken created OVIRT-2550: ----------------------------- Summary: Please add maintainers to pthreading project Key: OVIRT-2550 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2550 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra pthreading currently has no active maintainer, but has pending patches and ci issues to solve. Please grant admin rights to nsoffer and msobczyk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95011, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[CQ]: 91669,5 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

2 1

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2549: ---------------------------------- [~sbonazzo(a)redhat.com] can you please read mail from Miguel? we need to tag the correct package since upgrade fails in more then one project now. > master ovirt-engine fails on missing package > -------------------------------------------- > > Key: OVIRT-2549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2549: ----------------------------- Priority: Highest (was: Medium) > master ovirt-engine fails on missing package > -------------------------------------------- > > Key: OVIRT-2549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 91669,5 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 573 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Oct '18

18 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/573/ Build Number: 573 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #573 [Galit] Update the config for poll u/s sources ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7f158c2ca578> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37093, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type raise Error(msg) Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37093, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type raise Error(msg) 'The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7f158c2ca578>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37093, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault\n body = self._internal_read_body(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body\n self._connection.check_xml_content_type(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type\n response.headers\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type\n raise Error(msg)\nError: The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n--------------------- >> end captured logging << ---------------------'

1 2

[JIRA] (OVIRT-2548) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2548?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2548: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) wrong board > master ovirt-engine fails on missing package > --------------------------------------------- > > Key: OVIRT-2548 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2548 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_lago, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

Dafna Ron created OVIRT-2549: -------------------------------- Summary: master ovirt-engine fails on missing package Key: OVIRT-2549 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… change not related: https://gerrit.ovirt.org/#/c/94567/2 error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2548) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 18 Oct '18

18 Oct '18

Dafna Ron created OVIRT-2548: -------------------------------- Summary: master ovirt-engine fails on missing package Key: OVIRT-2548 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2548 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… change not related: https://gerrit.ovirt.org/#/c/94567/2 error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 94567,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Oct '18

18 Oct '18

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

2 1

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 86 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Oct '18

18 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build Number: 86 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #86 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 2

oVirt infra daily report - unstable production jobs - 616
by jenkins＠jenkins.phx.ovirt.org 18 Oct '18

18 Oct '18

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

1 0

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

17 Oct '18

Failed to run project_setup.sh for: #2282 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 ovirt-srv06.infra-phx.ovirt.org-container-6.

1 0

[JIRA] (OVIRT-2547) Fedora 28/rawhide job fail with: "Job for systemd-journald.service failed"
by Nir Soffer (oVirt JIRA) 17 Oct '18

17 Oct '18

Nir Soffer created OVIRT-2547: --------------------------------- Summary: Fedora 28/rawhide job fail with: "Job for systemd-journald.service failed" Key: OVIRT-2547 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2547 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra These jobs failed without running any test and no logs were collected. 1. 00:04:17.045 [check-patch.fc28.x86_64] Job for systemd-journald.service failed. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/617/consol… 2. 00:01:40.814 [check-patch.fcraw.x86_64] Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/618/consol… 3. 00:07:15.919 [check-patch.fc28.x86_64] Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/627/consol… Can we flag this kind of failure as CI error instead of test failure? Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

Fedora 28/rawhide job fail with: "Job for systemd-journald.service failed"
by Nir Soffer 17 Oct '18

17 Oct '18

These jobs failed without running any test and no logs were collected. 1. 00:04:17.045 [check-patch.fc28.x86_64] Job for systemd-journald.service failed. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/617/consol… 2. 00:01:40.814 [check-patch.fcraw.x86_64] Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/618/consol… 3. 00:07:15.919 [check-patch.fc28.x86_64] Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/627/consol… Can we flag this kind of failure as CI error instead of test failure? Nir

1 0

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

17 Oct '18

Failed to run project_setup.sh for: #2277 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 ovirt-srv05.phx.ovirt.org-container-7.

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 401 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Oct '18

17 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/401/ Build Number: 401 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #401 [Eitan Raviv] networking: connect NFS to engine over IPv6 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 012_local_maintenance_sdk.local_maintenance Error Message: 143 -------------------- >> begin captured logging << -------------------- root: INFO: * Waiting For System Stability... root: INFO: * Performing Deactivation... root: INFO: * Performing Activation... root: INFO: * Waiting For System Stability... cli: DEBUG: signal 15 was caught --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/he-node-ng-suite-4.2/test-scenarios/012_local_maintenance_sdk.py", line 79, in local_maintenance time.sleep(wait_value) File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 922, in exit_handler sys.exit(128 + signum) '143\n-------------------- >> begin captured logging << --------------------\nroot: INFO: * Waiting For System Stability...\nroot: INFO: * Performing Deactivation...\nroot: INFO: * Performing Activation...\nroot: INFO: * Waiting For System Stability...\ncli: DEBUG: signal 15 was caught\n--------------------- >> end captured logging << ---------------------'

1 9

[CQ]: 94823,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 17 Oct '18

17 Oct '18

Change 94823,3 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/94823/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10635/

1 0

[JIRA] (OVIRT-2424) Automate the reposync update process with an upstream-sources jenkins job
by Galit Rosenthal (oVirt JIRA) 17 Oct '18

17 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2424?page=com.atlassian.jira.… ] Galit Rosenthal updated OVIRT-2424: ----------------------------------- Assignee: Galit Rosenthal (was: infra) Status: In Progress (was: To Do) > Automate the reposync update process with an upstream-sources jenkins job > ------------------------------------------------------------------------- > > Key: OVIRT-2424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2424 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Galit Rosenthal > Assignee: Galit Rosenthal > > Add a job to Jenkins to update the different reposync -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2424) Automate the reposync update process with an upstream-sources jenkins job
by Galit Rosenthal (oVirt JIRA) 17 Oct '18

17 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2424?page=com.atlassian.jira.… ] Galit Rosenthal commented on OVIRT-2424: ---------------------------------------- Created the automation for the poll upstream A patch was sent to jenkins to run the job automatic > Automate the reposync update process with an upstream-sources jenkins job > ------------------------------------------------------------------------- > > Key: OVIRT-2424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2424 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Galit Rosenthal > Assignee: infra > > Add a job to Jenkins to update the different reposync -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 138 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Oct '18

17 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-pre_build-artifacts-… Build Number: 138 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #138 [Eyal Edri] Adding vstinner(a)redhat.com to whitelist [Evgheni Dereveanchin] Remove fcraw mirror sync job [Dafna Ron] Removed ovirt-provider-ovn v1 jobs [Sandro Bonazzola] Revert "Removed ovirt-provider-ovn v1 jobs" [Yuval Turgeman] build: add ovirt-engine-extension-aaa-ldap-setup ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 474 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Oct '18

17 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/474/ Build Number: 474 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #474 [Gal Ben Haim] OST container improvements ----------------- Failed Tests: ----------------- No tests ran.

1 1

missing python docker packages for OST?
by Francesco Romani 17 Oct '18

17 Oct '18

Hi all, I'm trying to run ovirt-system-tests-manual to test this patch: https://gerrit.ovirt.org/#/c/94947/ But I get this: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… this seems the root cause: *11:03:14* + sudo -n /bin/yum install -y python2-docker python3-docker *11:03:14* Loaded plugins: fastestmirror *11:03:14* Loading mirror speeds from cached hostfile *11:03:14* No package python2-docker available. *11:03:14* No package python3-docker available. *11:03:15* Error: Nothing to do *11:03:15* + local failed=0 *11:03:15* + for package in '"${packages[@]}"' *11:03:15* + rpm -q --quiet --whatprovides python2-docker *11:03:15* + log ERROR 'package '\''python2-docker'\'' is not, and could not be, installed' *11:03:15* + local level=ERROR *11:03:15* + shift *11:03:15* + local 'message=package '\''python2-docker'\'' is not, and could not be, installed' *11:03:15* + local prefix *11:03:15* + [[ 5 -gt 1 ]] *11:03:15* + prefix='global_setup[verify_packages]' *11:03:15* + echo 'global_setup[verify_packages] ERROR: package '\''python2-docker'\'' is not, and could not be, installed' *11:03:15* global_setup[verify_packages] ERROR: package 'python2-docker' is not, and could not be, installed *11:03:15* + (( ++failed )) Please suggest a fix for this Thanks, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

2 2

oVirt infra weekly meeting notes 17.10.2018
by Evgheni Dereveanchin 17 Oct '18

17 Oct '18

Hi everyone, Please find this week's infra updates below: PHX: - RAM monitoring added to resources - Outage reported by Nagios on Saturday, reason under investigation OVIRT-2536 <https://ovirt-jira.atlassian.net/browse/OVIRT-2536> - Intermediate Gerrit fetch issues reported OVIRT-2541 <https://ovirt-jira.atlassian.net/browse/OVIRT-2541> Other topics: - Gerrit migration OVIRT-2472 <https://ovirt-jira.atlassian.net/browse/OVIRT-2472> - EL7 system deployed - Secondary disk attached - Added to puppet and we can ansiblize the base OS - CVE-2018-10933 libssh vulnerability published - no CentOS patch yet - likely no impact on infra as Jenkins/Gerrit use Java SSH libs -- Regards, Evgheni Dereveanchin

1 0

[CQ]: 94647, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 17 Oct '18

17 Oct '18

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

2 1

[JIRA] (OVIRT-2546) 004_basic_sanity.verify_suspend_resume_vm0 failure on verify_suspend_resume_vm0 with no reason
by Dafna Ron (oVirt JIRA) 17 Oct '18

17 Oct '18

Dafna Ron created OVIRT-2546: -------------------------------- Summary: 004_basic_sanity.verify_suspend_resume_vm0 failure on verify_suspend_resume_vm0 with no reason Key: OVIRT-2546 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2546 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We had a failure on master ovirt-provider ovn project The change (https://gerrit.ovirt.org/#/c/94647/) had not caused the failure and I am not seeing any infra issue that can cause this failure. The build is: 'https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10625/' Here is the error: 'https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10625/testRe…' [~gbenhaim(a)redhat.com] can you please have a look before I move this to the developers? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 531 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Oct '18

17 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 531 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #531 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

17 Oct '18

Failed to run project_setup.sh for: #2264 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 ovirt-srv05.phx.ovirt.org-container-1.

1 0

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

17 Oct '18

Failed to run project_setup.sh for: #2264 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 ovirt-srv04.phx.ovirt.org-container-6.

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 727 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Oct '18

17 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 727 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #727 [Gal Ben Haim] OST container improvements ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_he_hosts Error Message: None != True after 900 seconds Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-ansible-suite-master/ovirt-system-tests/he-basic-ansible-suite-master/test-scenarios/002_bootstrap.py", line 358, in add_he_hosts add_he_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-ansible-suite-master/ovirt-system-tests/he-basic-ansible-suite-master/test-scenarios/002_bootstrap.py", line 404, in add_he_hosts_4 testlib.assert_true_within(_he_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 278, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: None != True after 900 seconds

1 1