ovirt_4.1_he-system-tests Failed!
by jenkins＠jenkins.phx.ovirt.org
------=_Part_20_1766333648.1489027049728
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/
Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/
Build Number: 34
Build Status: Still Failing
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #29
[Ondra Machacek] Add Ansible modules tests
[Sandro Bonazzola] pywin32-py2.7: drop fc24 on master
[Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master
[Eyal Edri] adding job for master ansible suite
Changes for Build #30
[Ondra Machacek] Add Ansible modules tests
Changes for Build #31
[Yaniv Kaul] Remove cockpit-ovirt installation test
Changes for Build #32
[Yaniv Kaul] Remove cockpit-ovirt installation test
[Yedidyah Bar David] ovirt-wgt: Built master only on fc25
[Greg Sheremeta] ovirt-engine-phantomjs: configure jobs
Changes for Build #33
[Yaniv Kaul] Slim down the amount of packages we sync
Changes for Build #34
[Yaniv Kaul] Slim down the amount of packages we sync
[Eyal Edri] remove emails from repo closure jobs
-----------------
Failed Tests:
-----------------
No tests ran.
------=_Part_20_1766333648.1489027049728--
8 years, 1 month
oVirt infra daily report - unstable production jobs - 256
by jenkins＠jenkins.phx.ovirt.org
------=_Part_16_907299769.1489359617015
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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/256//artifact/exported...
Cheers,
Jenkins
------=_Part_16_907299769.1489359617015
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 12/03/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.0_image-ng-system-tests/">ovirt_4.0_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
NOT STABLE YET
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_16_907299769.1489359617015--
8 years, 1 month
[ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]
by Daniel Belenky
*Test failed: *basic_sanity.hotplug_nic
*Link to failed job: *test-repo_ovirt_experimental_4.1/917/
<http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exp...>
*Link to all logs: *logs from Jenkins
<http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exp...>
*May be related to: *https://bugzilla.redhat.com/show_bug.cgi?id=1417595
*Error snippet from log: *(from supervdsm.log):
ifup/VLAN100_Network::DEBUG::2017-03-08
22:24:22,832::commands::93::root::(execCmd) FAILED: <err> = 'Running
scope as unit ff994cde-b66d-4d54-9e36-fc253682608f.scope.\n/etc/sysconfig/network-scripts/ifup-eth:
line 297: 16985 Terminated /sbin/dhclient ${DHCLIENTARGS}
${DEVICE}\nCannot find device "VLAN100_Network"\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\nDevice
"VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
exist.\nDevice "VLAN100_Network" does not exist.\n'; <rc> = 1
ifup/VLAN100_Network::ERROR::2017-03-08
22:24:22,832::utils::371::root::(wrapper) Unhandled exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper
return f(*a, **kw)
File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run
return func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py",
line 924, in _exec_ifup
_exec_ifup_by_name(iface.name, cgroup)
File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py",
line 910, in _exec_ifup_by_name
raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')
ConfigNetworkError: (29, 'Determining IPv6 information for
VLAN100_Network... failed.')
--
*Daniel Belenky*
*RHV DevOps*
*Red Hat Israel*
8 years, 1 month
[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1250:
-------------------------------------
We probably shouldn't just add everyone to the oVirt org. instead we should probably instruct the maintainers to run 'ci test please' to confirm the PR. (Or add to the org of they choose to)
> Github PR builder plugin generates too many messages
> ----------------------------------------------------
>
> Key: OVIRT-1250
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Pavel Zhukov
> Assignee: infra
>
> Seems like GH PR builder plugin posts one message like:
> Can one of the admins verify this patch?
> Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying.
--
This message was sent by Atlassian JIRA
(v1000.815.2#100035)
8 years, 1 month
[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jir... ]
eyal edri [Administrator] commented on OVIRT-1250:
--------------------------------------------------
Until we fix this, can we replace the message with something like: You're not part of the oVirt organization, please request one of the oVirt infra members to add you to be able to send PR requests.
> Github PR builder plugin generates too many messages
> ----------------------------------------------------
>
> Key: OVIRT-1250
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Pavel Zhukov
> Assignee: infra
>
> Seems like GH PR builder plugin posts one message like:
> Can one of the admins verify this patch?
> Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying.
--
This message was sent by Atlassian JIRA
(v1000.815.2#100035)
8 years, 1 month
[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jir... ]
eyal edri [Administrator] updated OVIRT-1252:
---------------------------------------------
Labels: standard-ci (was: )
> post-merge build-artifacts jobs can run out of order
> ----------------------------------------------------
>
> Key: OVIRT-1252
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Barak Korren
> Assignee: infra
> Labels: standard-ci
>
> Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel.
> The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order.
> To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available.
--
This message was sent by Atlassian JIRA
(v1000.815.2#100035)
8 years, 1 month
[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1252:
-----------------------------------
Summary: post-merge build-artifacts jobs can run out of order
Key: OVIRT-1252
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Barak Korren
Assignee: infra
Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel.
The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order.
To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available.
--
This message was sent by Atlassian JIRA
(v1000.815.2#100035)
8 years, 1 month
[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1252:
--------------------------------
Epic Link: OVIRT-400
> post-merge build-artifacts jobs can run out of order
> ----------------------------------------------------
>
> Key: OVIRT-1252
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Barak Korren
> Assignee: infra
>
> Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel.
> The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order.
> To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available.
--
This message was sent by Atlassian JIRA
(v1000.815.2#100035)
8 years, 1 month