- Infra - oVirt List Archives

[JIRA] (OVIRT-2467) Failed connect to gerrit.ovirt.org:443; No route to host
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2467?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2467: ---------------------------------- the job and logs are no longer available if this repeats we can re-open > Failed connect to gerrit.ovirt.org:443; No route to host > -------------------------------------------------------- > > Key: OVIRT-2467 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2467 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures, ost_infra > > Project name: > ovirt-ansible-engine-setup > Branch: > master > Failed Suite: > ovirt-master_change-queue-tester > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9260 > the root cause is that > oVirt_ovirt-ansible-engine-setup_standard-on-ghpush (29) failed building > and that is caused by: > https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-engine-setup_standard-on-… > 11:44:39 [build-artifacts.fc27.x86_64] ERROR: Error cloning remote repo 'origin' > 11:44:39 [build-artifacts.fc27.x86_64] hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: > 11:44:39 [build-artifacts.fc27.x86_64] stdout: > 11:44:39 [build-artifacts.fc27.x86_64] stderr: fatal: unable to access 'https://gerrit.ovirt.org/jenkins/': Failed connect to gerrit.ovirt.org:443; No route to host -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2468) ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2468?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2468: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory > -------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2468 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-engine > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7 > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9261/ > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory > 14:16:46 [upgrade-from-release-suite.el7.x86_64] Error while running thread > 14:16:46 [upgrade-from-release-suite.el7.x86_64] Traceback (most recent call last): > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 14:16:46 [upgrade-from-release-suite.el7.x86_64] queue.put({'return': func()}) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1524, in _collect_artifacts > 14:16:46 [upgrade-from-release-suite.el7.x86_64] vm.collect_artifacts(path, ignore_nopath) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 644, in collect_artifacts > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ignore_nopath=ignore_nopath > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 384, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] return self.provider.extract_paths(paths, *args, **kwargs) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", line 398, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ignore_nopath=ignore_nopath, > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 249, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] self._extract_paths_scp(paths=paths, ignore_nopath=ignore_nopath) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 83, in wrapper > 14:16:46 [upgrade-from-release-suite.el7.x86_64] return func(self, *args, **kwargs) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 279, in _extract_paths_scp > 14:16:46 [upgrade-from-release-suite.el7.x86_64] raise ExtractPathNoPathError(err.args[0]) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2468) ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2468?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2468: ---------------------------------- I am not sure what was the error but the job and logs are no longer available. I am closing this. if this happens again we can re-open > ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory > -------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2468 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-engine > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7 > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9261/ > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory > 14:16:46 [upgrade-from-release-suite.el7.x86_64] Error while running thread > 14:16:46 [upgrade-from-release-suite.el7.x86_64] Traceback (most recent call last): > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 14:16:46 [upgrade-from-release-suite.el7.x86_64] queue.put({'return': func()}) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1524, in _collect_artifacts > 14:16:46 [upgrade-from-release-suite.el7.x86_64] vm.collect_artifacts(path, ignore_nopath) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 644, in collect_artifacts > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ignore_nopath=ignore_nopath > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 384, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] return self.provider.extract_paths(paths, *args, **kwargs) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", line 398, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ignore_nopath=ignore_nopath, > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 249, in extract_paths > 14:16:46 [upgrade-from-release-suite.el7.x86_64] self._extract_paths_scp(paths=paths, ignore_nopath=ignore_nopath) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 83, in wrapper > 14:16:46 [upgrade-from-release-suite.el7.x86_64] return func(self, *args, **kwargs) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 279, in _extract_paths_scp > 14:16:46 [upgrade-from-release-suite.el7.x86_64] raise ExtractPathNoPathError(err.args[0]) > 14:16:46 [upgrade-from-release-suite.el7.x86_64] ExtractPathNoPathError: scp: /var/lib/pgsql/upgrade_rh-postgresql95-postgresql.log: No such file or directory -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2469) CQ Failure: can't install ovirt-host
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2469?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2469: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > CQ Failure: can't install ovirt-host > ------------------------------------- > > Key: OVIRT-2469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > yum install ovirt-host returns a package that does not exist under tested repo which is: > ovirt-imageio-common = 1.4.4-0.el7 > [~grosenth(a)redhat.com] is working on a fix to the reposync config file which will include that package. > 1) http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3035//artifact/b… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2469) CQ Failure: can't install ovirt-host
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2469?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2469: ---------------------------------- ovirt-engine is passing in both master and CQ. I am closing this as I am not seeing this failure any longer. please re-open if this is still happening. > CQ Failure: can't install ovirt-host > ------------------------------------- > > Key: OVIRT-2469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > yum install ovirt-host returns a package that does not exist under tested repo which is: > ovirt-imageio-common = 1.4.4-0.el7 > [~grosenth(a)redhat.com] is working on a fix to the reposync config file which will include that package. > 1) http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3035//artifact/b… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2484) ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2484?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2484: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument > ------------------------------------------------------------------------------------------------ > > Key: OVIRT-2484 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2484 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures > > seems we are getting random tests failure which I believe are caused by this error: > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line 220, in __call__ > self._func() > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 576, in __call__ > sample = HostSample(self._pid) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 240, in __init__ > self.interfaces = _get_interfaces_and_samples() > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 202, in _get_interfaces_and_samples > links_and_samples[link.name] = InterfaceSample(link) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 109, in __init__ > self.speed = _getLinkSpeed(link) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 590, in _getLinkSpeed > speed = vlan.speed(dev.name) > File "/usr/lib/python2.7/site-packages/vdsm/network/link/vlan.py", line 35, in speed > dev_speed = nic.read_speed_using_sysfs(dev_name) > File "/usr/lib/python2.7/site-packages/vdsm/network/link/nic.py", line 47, in read_speed_using_sysfs > s = int(f.read()) > IOError: [Errno 22] Invalid argument > ovirt 4.2 - migration test failed: > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3069/artifact/b… > master: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10176/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2484) ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2484?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2484: ---------------------------------- ovirt-engine is passing now in both 4.2 and master. > ovirt engine master and 4.2 are failing on random tests with possible cause an Invalid argument > ------------------------------------------------------------------------------------------------ > > Key: OVIRT-2484 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2484 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures > > seems we are getting random tests failure which I believe are caused by this error: > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/virt/periodic.py", line 220, in __call__ > self._func() > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 576, in __call__ > sample = HostSample(self._pid) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 240, in __init__ > self.interfaces = _get_interfaces_and_samples() > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 202, in _get_interfaces_and_samples > links_and_samples[link.name] = InterfaceSample(link) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 109, in __init__ > self.speed = _getLinkSpeed(link) > File "/usr/lib/python2.7/site-packages/vdsm/virt/sampling.py", line 590, in _getLinkSpeed > speed = vlan.speed(dev.name) > File "/usr/lib/python2.7/site-packages/vdsm/network/link/vlan.py", line 35, in speed > dev_speed = nic.read_speed_using_sysfs(dev_name) > File "/usr/lib/python2.7/site-packages/vdsm/network/link/nic.py", line 47, in read_speed_using_sysfs > s = int(f.read()) > IOError: [Errno 22] Invalid argument > ovirt 4.2 - migration test failed: > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3069/artifact/b… > master: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10176/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2494) CQ Failure - Cannot add host
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2494?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2494: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > CQ Failure - Cannot add host > ---------------------------- > > Key: OVIRT-2494 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2494 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, OST > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > Hi, > This is an example of a he basic suite master that fails on : > Error Message: > 00:26:36 Error while running thread > 00:26:36 Traceback (most recent call last): > 00:26:36 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 00:26:36 queue.put({'return': func()}) > 00:26:36 File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 379, in _add_he_host_4 > 00:26:36 deploy_hosted_engine=True, > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 11530, in add > 00:26:36 return self._internal_add(host, headers, query, wait) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _internal_add > 00:26:36 return future.wait() if wait else future > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait > 00:26:36 return self._code(response) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229, in callback > 00:26:36 self._check_fault(response) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault > 00:26:36 self._raise_error(response, body) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error > 00:26:36 raise error > 00:26:36 Error: Fault reason is "Operation Failed". Fault detail is "[Cannot add Host. You are using an unmanaged hosted engine VM. Please add the first storage domain in order to start the hosted engine import process.]". HTTP response code is 409. > Job url: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > There is a patch which was merged: > https://gerrit.ovirt.org/#/c/94219/ > It did not pass CQ because of another failure which Ravi is working on ( Add cluster issue). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2494) CQ Failure - Cannot add host
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2494?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2494: ---------------------------------- ovirt-engine is passing and I can confirm this was solved. > CQ Failure - Cannot add host > ---------------------------- > > Key: OVIRT-2494 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2494 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, OST > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures > > Hi, > This is an example of a he basic suite master that fails on : > Error Message: > 00:26:36 Error while running thread > 00:26:36 Traceback (most recent call last): > 00:26:36 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 00:26:36 queue.put({'return': func()}) > 00:26:36 File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 379, in _add_he_host_4 > 00:26:36 deploy_hosted_engine=True, > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 11530, in add > 00:26:36 return self._internal_add(host, headers, query, wait) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _internal_add > 00:26:36 return future.wait() if wait else future > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait > 00:26:36 return self._code(response) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229, in callback > 00:26:36 self._check_fault(response) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault > 00:26:36 self._raise_error(response, body) > 00:26:36 File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error > 00:26:36 raise error > 00:26:36 Error: Fault reason is "Operation Failed". Fault detail is "[Cannot add Host. You are using an unmanaged hosted engine VM. Please add the first storage domain in order to start the hosted engine import process.]". HTTP response code is 409. > Job url: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > There is a patch which was merged: > https://gerrit.ovirt.org/#/c/94219/ > It did not pass CQ because of another failure which Ravi is working on ( Add cluster issue). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2496) master ovirt-engine is failing on 002_bootstrap.add_hosts in upgrade suite
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2496?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2496: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > master ovirt-engine is failing on 002_bootstrap.add_hosts in upgrade suite > --------------------------------------------------------------------------- > > Key: OVIRT-2496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2496 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > we have a new regression after the previous one was fixed. > the issue is in the upgrade suite with test 002_bootstrap.add_hosts. > full logs: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… > error: https://pastebin.com/B5wxKTJy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2496) master ovirt-engine is failing on 002_bootstrap.add_hosts in upgrade suite
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2496?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2496: ---------------------------------- fix: https://gerrit.ovirt.org/94357 we have a passing CQ and a new package in tested. > master ovirt-engine is failing on 002_bootstrap.add_hosts in upgrade suite > --------------------------------------------------------------------------- > > Key: OVIRT-2496 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2496 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > we have a new regression after the previous one was fixed. > the issue is in the upgrade suite with test 002_bootstrap.add_hosts. > full logs: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… > error: https://pastebin.com/B5wxKTJy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

PLEASE READ: Stop merging to ovirt-engine master until further notice
by Dafna Ron 17 Sep '18

17 Sep '18

Hello to all, I asked to stop merging last week but it seemed to have been ignored so writing again. *please stop merging to ovirt-engine master until further notice.* the project has been failing for the last two weeks on various different regressions. You continue to merge changes which means that you are risking further regressions and making it hard to stabilize the master branch for ovirt-engine. to make it clear: 1. all changes that were merged since sept. 4th to the master branch exist only in the ovirt-engine master branch (i.e they are not included in your project package). 2. any code merged to master in the past two weeks was most likely not tested by CQ since we exit on first test failure (if your code effects anything after the reported issues ran, they would not be tested). 3. you are putting other projects at risk for regressions since they are tested with a 2 weeks old ovirt-engine packages. Thanks you. Dafna

1 1

[JIRA] (OVIRT-2498) Failing KubeVirt CI
by Petr Kotas (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2498?page=com.atlassian.jira.… ] Petr Kotas commented on OVIRT-2498: ----------------------------------- I have created the issue. The failures in the stdci are only partially causing our failures. Most of the failures are due to unknown timeouts. For this I would like to see live load on the test machine. If this can be done. Thanks in advance. Best, Petr On Mon, Sep 17, 2018 at 4:18 PM Barak Korren (oVirt JIRA) < > Failing KubeVirt CI > ------------------- > > Key: OVIRT-2498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > I am working on fixing the issues on the KubeVirt e2e test suites. This > task is directly related to unstable CI, due to unknown errors. > The progress is reported in the CNV trello: > https://trello.com/c/HNXcMEQu/161-epic-improve-ci > I am creating this issue since the KubeVirt experience random timeouts on > random tests most of the times when test suites run. > The issue from outside is showing as timeouts on difference part of tests. > Sometimes the tests fails in set up phase, again due to random timeout. > The example in the link bellow timed out for network connection on > localhost. > [check-patch.k8s-1.11.0-dev.el7.x86_64] > requests.exceptions.ReadTimeout: > UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. > (read timeout=60) > Example of failing test suites is here > https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/cons… > The list of errors related to the failing CI can be found in my notes > https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJFT… > I am not sure whether KubeVirt already shared the resource requirements, so > I provide short summary: > *Resources for KubeVirt e2e tests:* > - at least 12GB of RAM - we start 3 nodes (3 docker images) each require > 4GB of RAM > - exposed /dev/kvm to enable native virtualization > - cached images, since these are used to build the test cluster: > - kubevirtci/os-3.10.0-crio:latest > - kubevirtci/os-3.10.0-multus:latest > - kubevirtci/os-3.10.0:latest > - kubevirtci/k8s-1.10.4:latest > - kubevirtci/k8s-multus-1.11.1:latest > - kubevirtci/k8s-1.11.0:latest > How can we overcome this? Can we work together to build a suitable > requirements for running the tests so it passes each time? > Kind regards, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Petr Kotas (oVirt JIRA) 17 Sep '18

17 Sep '18

Petr Kotas created OVIRT-2504: --------------------------------- Summary: standard CI fails in project_setup phase Key: OVIRT-2504 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Petr Kotas Assignee: infra Hi, the standard CI is failing in project_setup phase. Can you please debug that? The issue is somehow related to docker clean up phase. Example of failing CI is : - https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… - https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… - https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… Unfortunately, the logs are the only thing I can see. From our side, there is nothing special. Just normal test run. We did not tune anything. Thank you, Best, Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2503) Testing automatic Jira ticket logging for CQ monitoring
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

Dafna Ron created OVIRT-2503: -------------------------------- Summary: Testing automatic Jira ticket logging for CQ monitoring Key: OVIRT-2503 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2503 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra As part of monitoring improvement and shifting partial responsibility for CQ monitoring to the developers I would like to do some experiments on connecting CQ alerts to create Jira tickets automatically. As we have the ost monitoring project we start by doing some tests on that project so that we do not overflow our jira with alerts. For now I would like to start with Jira's opening with the following specifications: 1. Subject: [ CQ ] [$patch number] [ oVirt $VER ($project) ] [ TEST NAME ] 2. at the beginning, email sent to: dron(a)redhat.com 3. jira description [cq message] 4. all jira's has to have label=ost_failure and infra-owner as default. I would like to change the project type to allow: 1. easy closing of Jira's (one/two clicks if we can) 2. view of Jira's like service tickets (rather then bugs) There is a plugin called zapier that allows to easily connect a jira from an email and also allow to add some rules to the Jira which may make this easier for us. can you also install it and link it to the ost jira? I have an email account that we can use for that. cq.ovirt(a)gmail.com https://zapier.com/apps/jira/integrations [~bkorren(a)redhat.com] once I do some tests on my own on this, I wanted to try and collaborate with one of the projects (maybe networking or one of sandro's teams) where CQ failures would automatically open a ticket to their team and they can handle the monitoring and escalate issues to us if needed. Any advice on configurations we should be thinking of for that? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2498) Failing KubeVirt CI
by Barak Korren (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2498?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2498: ------------------------------------- [~pkotas] ok, I see its failing in the docketr-cleaup script... hmm.. we'll need to debug that... Can you please open a specific ticket on that and include logs and any other specific information that can help us figure out why it may be failing there... (What containers might be on the machine that its failing to remove...) But that is not what is causing all the failures right? We already fixed a couple of issues with that script... > Failing KubeVirt CI > ------------------- > > Key: OVIRT-2498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > I am working on fixing the issues on the KubeVirt e2e test suites. This > task is directly related to unstable CI, due to unknown errors. > The progress is reported in the CNV trello: > https://trello.com/c/HNXcMEQu/161-epic-improve-ci > I am creating this issue since the KubeVirt experience random timeouts on > random tests most of the times when test suites run. > The issue from outside is showing as timeouts on difference part of tests. > Sometimes the tests fails in set up phase, again due to random timeout. > The example in the link bellow timed out for network connection on > localhost. > [check-patch.k8s-1.11.0-dev.el7.x86_64] > requests.exceptions.ReadTimeout: > UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. > (read timeout=60) > Example of failing test suites is here > https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/cons… > The list of errors related to the failing CI can be found in my notes > https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJFT… > I am not sure whether KubeVirt already shared the resource requirements, so > I provide short summary: > *Resources for KubeVirt e2e tests:* > - at least 12GB of RAM - we start 3 nodes (3 docker images) each require > 4GB of RAM > - exposed /dev/kvm to enable native virtualization > - cached images, since these are used to build the test cluster: > - kubevirtci/os-3.10.0-crio:latest > - kubevirtci/os-3.10.0-multus:latest > - kubevirtci/os-3.10.0:latest > - kubevirtci/k8s-1.10.4:latest > - kubevirtci/k8s-multus-1.11.1:latest > - kubevirtci/k8s-1.11.0:latest > How can we overcome this? Can we work together to build a suitable > requirements for running the tests so it passes each time? > Kind regards, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2498) Failing KubeVirt CI
by Petr Kotas (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2498?page=com.atlassian.jira.… ] Petr Kotas commented on OVIRT-2498: ----------------------------------- [~bkorren(a)redhat.com] I would like to see the machine resources. The use of CPU, the use of RAM to understand how the tests behave live. I am not sure whether this is working on Blue Ocean. WRT the docker, as I already pointer in the logs. The issue is way before our setup even kicks in. [Here|https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt…] is the direct link for that. It seems that the jenkins project_setup.sh fails somehow. Again this is not our code, it is part of standard ci located [here|https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/shel…] It seems that the project setup, was doing its job and than randomly failed due to networking issue. I have no idea why. Also I do not thing the issue is due to proxy as the failures are totally random on random tests. So I am guessing something more hidden fails. > Failing KubeVirt CI > ------------------- > > Key: OVIRT-2498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > I am working on fixing the issues on the KubeVirt e2e test suites. This > task is directly related to unstable CI, due to unknown errors. > The progress is reported in the CNV trello: > https://trello.com/c/HNXcMEQu/161-epic-improve-ci > I am creating this issue since the KubeVirt experience random timeouts on > random tests most of the times when test suites run. > The issue from outside is showing as timeouts on difference part of tests. > Sometimes the tests fails in set up phase, again due to random timeout. > The example in the link bellow timed out for network connection on > localhost. > [check-patch.k8s-1.11.0-dev.el7.x86_64] > requests.exceptions.ReadTimeout: > UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. > (read timeout=60) > Example of failing test suites is here > https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/cons… > The list of errors related to the failing CI can be found in my notes > https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJFT… > I am not sure whether KubeVirt already shared the resource requirements, so > I provide short summary: > *Resources for KubeVirt e2e tests:* > - at least 12GB of RAM - we start 3 nodes (3 docker images) each require > 4GB of RAM > - exposed /dev/kvm to enable native virtualization > - cached images, since these are used to build the test cluster: > - kubevirtci/os-3.10.0-crio:latest > - kubevirtci/os-3.10.0-multus:latest > - kubevirtci/os-3.10.0:latest > - kubevirtci/k8s-1.10.4:latest > - kubevirtci/k8s-multus-1.11.1:latest > - kubevirtci/k8s-1.11.0:latest > How can we overcome this? Can we work together to build a suitable > requirements for running the tests so it passes each time? > Kind regards, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[CQ]: 94357, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Sep '18

17 Sep '18

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

1 0

[JIRA] (OVIRT-2502) official releases not being tested by change queue
by sbonazzo (oVirt JIRA) 17 Sep '18

17 Sep '18

sbonazzo created OVIRT-2502: ------------------------------- Summary: official releases not being tested by change queue Key: OVIRT-2502 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2502 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, just noticed in https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… that both the patch including the official release patch and the post-release patch has been added to the same change queue job, causing the official release to be skipped in favor of the post release: - Started by upstream project ovirt-4.2_change-queue <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8642 <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8642/> originally caused by: - Started by upstream project standard-enqueue <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16477 <https://jenkins.ovirt.org/job/standard-enqueue/16477/> originally caused by: - Triggered by Gerrit: https://gerrit.ovirt.org/94367 Other triggered builds for this event. ovirt-engine_4.2_build-artifacts-el7-x86_64 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> #828 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> ovirt-engine_4.2_check-merged-el7-x86_64 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> #800 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/800/> - Started by upstream project ovirt-4.2_change-queue <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8643 <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8643/> originally caused by: - Started by upstream project standard-enqueue <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16478 <https://jenkins.ovirt.org/job/standard-enqueue/16478/> originally caused by: - Triggered by Gerrit: https://gerrit.ovirt.org/94368 Other triggered builds for this event. ovirt-engine_4.2_build-artifacts-el7-x86_64 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> #829 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> ovirt-engine_4.2_check-merged-el7-x86_64 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> #801 <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/801/> This is really bad, meaning that a regression introduced in the release patch may be completely ignored provided that the post release patch fixes it. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2497) ovirt-master in project vdsm failing on migrate vm test
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2497?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2497: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-master in project vdsm failing on migrate vm test > ------------------------------------------------------- > > Key: OVIRT-2497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2497 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > we have a failure in migrate vm for project vdsm > full logs can be found here: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10309/artifa… > reported patch and root cause patch do not seem related to the failure. > I suspect this is the change that caused the issue: > https://gerrit.ovirt.org/#/c/94248/ > error: https://pastebin.com/XNGFgfvL -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2497) ovirt-master in project vdsm failing on migrate vm test
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2497?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2497: ---------------------------------- https://gerrit.ovirt.org/#/c/94347/ this was fixed. > ovirt-master in project vdsm failing on migrate vm test > ------------------------------------------------------- > > Key: OVIRT-2497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2497 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > we have a failure in migrate vm for project vdsm > full logs can be found here: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10309/artifa… > reported patch and root cause patch do not seem related to the failure. > I suspect this is the change that caused the issue: > https://gerrit.ovirt.org/#/c/94248/ > error: https://pastebin.com/XNGFgfvL -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 14-08-2018 ] [ 006_migrations.migrate_vm ]
by Dafna Ron 17 Sep '18

17 Sep '18

Hi, We have a failure in vm migration on project vdsm master branch. I think the issue is related to this change: https://gerrit.ovirt.org/#/c/94248/ - https://gerrit.ovirt.org/#/c/94248/ Can you please have a look? full logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10309/artifa… error: 2018-09-14 07:15:43,102-0400 ERROR (migsrc/ade7210f) [virt.vm] (vmId='ade7210f-992e-4256-a33f-1340552892c9') __init__() takes exactly 3 arguments (2 given) (migration:281) 2018-09-14 07:15:43,102-0400 DEBUG (migsrc/ade7210f) [jsonrpc.Notification] Sending event {"params": {"notify_time": 4296575510, "ade7210f-992e-4256-a33f-1340552892c9": {"status": "Up"}}, "jsonrpc": "2.0", "method": "|virt|VM_status|ade72 10f-992e-4256-a33f-1340552892c9"} (__init__:181) 2018-09-14 07:15:43,103-0400 DEBUG (JsonRpc (StompReactor)) [yajsonrpc.protocols.stomp.AsyncClient] Stomp connection established (stompclient:138) 2018-09-14 07:15:43,104-0400 DEBUG (migsrc/ade7210f) [vds] Sending notification |virt|VM_status|ade7210f-992e-4256-a33f-1340552892c9 with params {'notify_time': 4296575510, 'ade7210f-992e-4256-a33f-1340552892c9': {'status': 'Up'}} (clien tIF:225) 2018-09-14 07:15:43,104-0400 ERROR (migsrc/ade7210f) [virt.vm] (vmId='ade7210f-992e-4256-a33f-1340552892c9') Failed to migrate (migration:449) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 401, in _regular_run self._setupVdsConnection() File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 241, in _setupVdsConnection self._destServer = jsonrpcvdscli.connect(requestQueue, client) File "/usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py", line 259, in connect return _Server(client, xml_compat) File "/usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py", line 135, in __init__ self._schema = vdsmapi.Schema.vdsm_api(api_strict_mode) File "/usr/lib/python2.7/site-packages/vdsm/api/vdsmapi.py", line 155, in vdsm_api return Schema(schema_types, *args, **kwargs) TypeError: __init__() takes exactly 3 arguments (2 given)

2 3

[oVirt Jenkins] ovirt-appliance_4.2_build-artifacts-el7-x86_64 - Build # 197 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_64… Build Number: 197 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #197 [Gal Ben Haim] Add jobs for ovs-cni [Yuval Turgeman] build: add ovirt-engine-extension-aaa-ldap-setup ----------------- Failed Tests: ----------------- No tests ran.

1 4

jira issues for didi
by Yedidyah Bar David 17 Sep '18

17 Sep '18

Hi all, Yesterday I sent an email to infra-support (with subject "Add gerrit comment about actual CQ results"). I didn't receive any automatic notification or anything. I now logged into jira with my account there (ybardavi) and noticed there is a pending request I made some time ago to change my email there to didi at redhat. I tried finishing the process but whatever I did it failed. I then searched all tickets reported by didi at redhat and see that last one I can find is from Apr, and the next ones (total 4, including the one from yesterday) were not found. So somehow the address didi at redhat is marked as spammer, or problematic in some other way... I see these options now: 1. Just ignore this, do not use jira, do not email infra-support, use the web interface when I must. 2. Have someone (who?) fix this - either assign the address didi at redhat as a valid address for my existing account, or change my email address there, or something like that. 3. Configure my mail client (gmail web interface) to use ybardavi at redhat when sending email to infra-support. I guess/hope this is possible, didn't try yet. I don't like this option, because I prefer to use didi@, and it has the downside of having data there with both addresses unrelated to each other, but it's obviously the simplest. Fixes/opinions/ideas/etc are welcome :-) Thanks, -- Didi

2 3

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 55 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build Number: 55 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #55 [Yuval Turgeman] stdci: move build-artifacts to a v1 job ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2463) http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
by Ehud Yonasi (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2463?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2463: ------------------------------------ We've discussed on IRC, and you've been able to install engine > http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2463 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2463 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-ansible-engine-setup > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7.x86_64 > Failed test/failed phase: > 001_upgrade_engine.test_initialize_engine > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/ > Link to first reported failed patch: > ??? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2498) Failing KubeVirt CI
by Barak Korren (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2498?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2498: ------------------------------------- [~pkotas] please be more specific about what you mean by monitoring access. you should already be able to monitor the job as it runs in multiple ways via Blue Ocean, the Jenkins old UI or the STDCI UI. WRT Docker connection issues - where is the Docker command being lunched? If its launched from inside the containers that Kubevirt-CI creates, then its really not something I can control (AFAIK its sets up its own networking inside a special "dnsmasq" container). If the thing that fails tries to connect directly from the STDCI environemnt to some service, it may have to do with the fact that we have a proxy configured in the environment. you ned to make sure the connections you're trying to setup and not being routed via the proxy by either setting the 'no_proxy' env var or unsetting the 'http_proxy' env var. I added code to do this in Kubevirt's test.sh a while ago, but maybe someone removed it. > Failing KubeVirt CI > ------------------- > > Key: OVIRT-2498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > I am working on fixing the issues on the KubeVirt e2e test suites. This > task is directly related to unstable CI, due to unknown errors. > The progress is reported in the CNV trello: > https://trello.com/c/HNXcMEQu/161-epic-improve-ci > I am creating this issue since the KubeVirt experience random timeouts on > random tests most of the times when test suites run. > The issue from outside is showing as timeouts on difference part of tests. > Sometimes the tests fails in set up phase, again due to random timeout. > The example in the link bellow timed out for network connection on > localhost. > [check-patch.k8s-1.11.0-dev.el7.x86_64] > requests.exceptions.ReadTimeout: > UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. > (read timeout=60) > Example of failing test suites is here > https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/cons… > The list of errors related to the failing CI can be found in my notes > https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJFT… > I am not sure whether KubeVirt already shared the resource requirements, so > I provide short summary: > *Resources for KubeVirt e2e tests:* > - at least 12GB of RAM - we start 3 nodes (3 docker images) each require > 4GB of RAM > - exposed /dev/kvm to enable native virtualization > - cached images, since these are used to build the test cluster: > - kubevirtci/os-3.10.0-crio:latest > - kubevirtci/os-3.10.0-multus:latest > - kubevirtci/os-3.10.0:latest > - kubevirtci/k8s-1.10.4:latest > - kubevirtci/k8s-multus-1.11.1:latest > - kubevirtci/k8s-1.11.0:latest > How can we overcome this? Can we work together to build a suitable > requirements for running the tests so it passes each time? > Kind regards, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2498) Failing KubeVirt CI
by Petr Kotas (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2498?page=com.atlassian.jira.… ] Petr Kotas commented on OVIRT-2498: ----------------------------------- Hi Barak, I understand and agree that mailing list is a great place to share the knowledge. I will write a summary there once we come up with a solution for this issue. And we need to figure the solution swiftly as TLV has holidays approaching. The issues I have described are recurring for almost a 3 months and are blocking us to progress with our work. We already work on fixing the issue from our site and are working on additional fixes to provide even more stable tests. The other part is be sure, we are not crashing the CI. Would you be able to give me a monitoring access so I can see whether there are any race conditions, or we deplete some resources? Regarding the timeouts. We are not relying on them. The timeout you have seen in the logs, is from your infrastructure. It signals, there is networking issue and the docker cannot connect to localhost, which is weird. So please, can I have monitoring access? And can you please check whether the network does not have any issues? Thank you for your help! I appreciate it. Best, Petr On Sun, Sep 16, 2018 at 8:08 AM Barak Korren (oVirt JIRA) < > Failing KubeVirt CI > ------------------- > > Key: OVIRT-2498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2498 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > I am working on fixing the issues on the KubeVirt e2e test suites. This > task is directly related to unstable CI, due to unknown errors. > The progress is reported in the CNV trello: > https://trello.com/c/HNXcMEQu/161-epic-improve-ci > I am creating this issue since the KubeVirt experience random timeouts on > random tests most of the times when test suites run. > The issue from outside is showing as timeouts on difference part of tests. > Sometimes the tests fails in set up phase, again due to random timeout. > The example in the link bellow timed out for network connection on > localhost. > [check-patch.k8s-1.11.0-dev.el7.x86_64] > requests.exceptions.ReadTimeout: > UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. > (read timeout=60) > Example of failing test suites is here > https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/cons… > The list of errors related to the failing CI can be found in my notes > https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJFT… > I am not sure whether KubeVirt already shared the resource requirements, so > I provide short summary: > *Resources for KubeVirt e2e tests:* > - at least 12GB of RAM - we start 3 nodes (3 docker images) each require > 4GB of RAM > - exposed /dev/kvm to enable native virtualization > - cached images, since these are used to build the test cluster: > - kubevirtci/os-3.10.0-crio:latest > - kubevirtci/os-3.10.0-multus:latest > - kubevirtci/os-3.10.0:latest > - kubevirtci/k8s-1.10.4:latest > - kubevirtci/k8s-multus-1.11.1:latest > - kubevirtci/k8s-1.11.0:latest > How can we overcome this? Can we work together to build a suitable > requirements for running the tests so it passes each time? > Kind regards, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-fc28-x86_64 - Build # 62 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build Number: 62 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #62 [Yuval Turgeman] automation: remove build-artifacts* from stdci-v2 ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results
by Emil Natan (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2501: ------------------------------ Resolution: Duplicate Status: Done (was: To Do) duplicates - OVIRT-1447 > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[CQ Failure Report] [oVirt Master - ovirt-engine] [16/9/18] [basic-suite.el7.x86_64]
by Ehud Yonasi 17 Sep '18

17 Sep '18

Hey everyone, We have a failure in CQ on the test of verify_add_hosts. Link to error: https://pastebin.com/Bwqn19Pn Link to the CQ job: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change…

2 1

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results
by Emil Natan (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jira.… ] Emil Natan commented on OVIRT-2501: ----------------------------------- duplicates OVIRT-1447 > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2501: ---------------------------------- CQ is not completely automated and what I mean by that is that we (i.e me/infra owners) need to look at the failures and determine if the cause of failure/root cause of failure or some other patch is responsible. Having said that, we want, in future, to involve the developers automatically at an earlier stage then this one but we are still considering several solutions for this. > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 197 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/1… Build Number: 197 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #197 [Gal Ben Haim] Add jobs for ovs-cni [Ryan Barry] kickstart: let VDSM reconfigure itself ----------------- Failed Tests: ----------------- No tests ran.

1 4

[JIRA] (OVIRT-2463) http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
by Yedidyah Bar David (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2463?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-2463: ------------------------------------------- Any update? https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… 06:03:03 + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie 06:03:03 http://192.168.200.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found 06:03:03 Error: Package: ovirt-engine-4.3.0-0.0.master.20180916101831.gitd855858.el7.noarch (alocalsync) 06:03:03 Requires: nimbus-jose-jwt >= 5.12 > http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2463 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2463 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-ansible-engine-setup > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7.x86_64 > Failed test/failed phase: > 001_upgrade_engine.test_initialize_engine > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/ > Link to first reported failed patch: > ??? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results
by Yedidyah Bar David (oVirt JIRA) 17 Sep '18

17 Sep '18

Yedidyah Bar David created OVIRT-2501: ----------------------------------------- Summary: Add gerrit comment about actual CQ results Key: OVIRT-2501 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Yedidyah Bar David Assignee: infra Hi all, I do not know how the CQ works, or even the terminology. Sorry. When a patch is merged in gerrit, some time later a job is triggered that adds it to the CQ. This job adds a link like [1]. Later, the CQ tests the batch of changes, and either approves them or bisects them to try to find the bad one. I can't see in the gerrit page, e.g. [2], any comment from this part. Please make the relevant jobs add suitable comments to relevant gerrit changes. E.g. "This change passed the CQ <link>", or failed, or some other suspect change failed and therefore this one isn't published either, or whatever. [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1869
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1869/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision f9508e32027645ea57bcfec09dafe628fbb06677 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f9508e32027645ea57bcfec09dafe628fbb06677 Commit message: "standard_pipelines: add nmstate project" > git rev-list --no-walk f9508e32027645ea57bcfec09dafe628fbb06677 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins2411326242761979621.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/packages' Build step 'Execute shell' marked build as failure

1 1

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #343
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

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

1 3

oVirt infra daily report - unstable production jobs - 585
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 168 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Sep '18

16 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/168/ Build Number: 168 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #168 [Milan Zamazal] Update test-vm.ovf file [Ehud Yonasi] standard_pipelines: add nmstate project ----------------- Failed Tests: ----------------- No tests ran.

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1867
by jenkins＠jenkins.phx.ovirt.org 16 Sep '18

16 Sep '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1867/displ…> Changes: [Ehud Yonasi] standard_pipelines: add nmstate project ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision f9508e32027645ea57bcfec09dafe628fbb06677 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f9508e32027645ea57bcfec09dafe628fbb06677 Commit message: "standard_pipelines: add nmstate project" > git rev-list --no-walk 9c187d6e9145db35423f495b553304ceb75489cb # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins8693387341267238789.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 209, in main my.doSackSetup(arches) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 741, in doSackSetup return self._getSacks(archlist=archlist, thisrepo=thisrepo) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 256, in populate ret = misc.repo_gen_decompress(xml, gen, cached=repo.cache) File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1165, in repo_gen_decompress return decompress(filename, dest=dest, check_timestamps=True) File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1150, in decompress _decompress_chunked(filename, out, ztype) File "/usr/lib/python2.7/site-packages/yum/misc.py", line 791, in _decompress_chunked raise Errors.MiscError, msg yum.Errors.MiscError: Error reading from file /home/jenkins/mirrors_cache/epel-el6/e9f08db71fa5910b2244b7d00b78a96ebb4eae598bcb011dda4bb7cf3e15ec04-primary.xml.gz: Not a gzipped file Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 571 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Sep '18

16 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/… Build Number: 571 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #571 [Milan Zamazal] Update test-vm.ovf file ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 581 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Sep '18

16 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/581/ Build Number: 581 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #581 [Milan Zamazal] Update test-vm.ovf file ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 681 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 Sep '18

16 Sep '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/68… Build Number: 681 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #681 [Milan Zamazal] Update test-vm.ovf file ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

16 Sep '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: 635 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #635 [Milan Zamazal] Update test-vm.ovf file ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL
by Daniel Belenky (oVirt JIRA) 16 Sep '18

16 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2500?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2500: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Support for notifications configuration in STDCI DSL > ---------------------------------------------------- > > Key: OVIRT-2500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As a developer, I want to have the ability to configure different aspects of the CI system's notifications: who receives the notifications (the change/tag owner, list of maintainers, etc), what kind of notifications are sent (notify SCM, notify mail, etc) so that I wont miss important events in my proejct. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL
by Daniel Belenky (oVirt JIRA) 16 Sep '18

16 Sep '18

Daniel Belenky created OVIRT-2500: ------------------------------------- Summary: Support for notifications configuration in STDCI DSL Key: OVIRT-2500 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra As a developer, I want to have the ability to configure different aspects of the CI system's notifications: who receives the notifications (the change/tag owner, list of maintainers, etc), what kind of notifications are sent (notify SCM, notify mail, etc) so that I wont miss important events in my proejct. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL
by Daniel Belenky (oVirt JIRA) 16 Sep '18

16 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2500?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2500: ---------------------------------- Epic Link: OVIRT-2499 > Support for notifications configuration in STDCI DSL > ---------------------------------------------------- > > Key: OVIRT-2500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As a developer, I want to have the ability to configure different aspects of the CI system's notifications: who receives the notifications (the change/tag owner, list of maintainers, etc), what kind of notifications are sent (notify SCM, notify mail, etc) so that I wont miss important events in my proejct. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2499) Add support for tag stage in STDCI
by Daniel Belenky (oVirt JIRA) 16 Sep '18

16 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2499?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2499: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support for tag stage in STDCI > ---------------------------------- > > Key: OVIRT-2499 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2499 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As a developer, I want to have the ability to run my automation code upon new tags being pushed to my project so that I can trigger an automated release process. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2499) Add support for tag stage in STDCI
by Daniel Belenky (oVirt JIRA) 16 Sep '18

16 Sep '18

Daniel Belenky created OVIRT-2499: ------------------------------------- Summary: Add support for tag stage in STDCI Key: OVIRT-2499 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2499 Project: oVirt - virtualization made easy Issue Type: Epic Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra As a developer, I want to have the ability to run my automation code upon new tags being pushed to my project so that I can trigger an automated release process. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0