Jenkins check-merged failures
by Milan Zamazal
Hi,
a series of 4 my Vdsm patches was merged yesterday and Jenkins has
failed on two of them in check-merged. See
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1504/
and
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1506/.
The corresponding errors were:
16:20:09 + lago ovirt deploy
16:20:09 current session does not belong to lago group.
16:20:09 @ Deploy oVirt environment:
16:20:09 # ovirt-role metadata entry will be soon deprecated, instead you should use the vm-provider entry in the domain definition and set it no one of: ovirt-node, ovirt-engine, ovirt-host
16:20:09 # Deploy environment:
16:20:09 * [Thread-2] Deploy VM vdsm_functional_tests_host-el7:
16:20:23 - STDERR
16:20:23
16:20:23
16:20:23 Exiting on user cancel
16:20:23
16:20:23 * [Thread-2] Deploy VM vdsm_functional_tests_host-el7: ERROR (in 0:00:13)
16:20:23 Error while running thread
16:20:23 Traceback (most recent call last):
16:20:23 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue
16:20:23 queue.put({'return': func()})
16:20:23 File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1339, in _deploy_host
16:20:23 host.name(),
16:20:23 RuntimeError: /home/jenkins/workspace/vdsm_master_check-merged-el7-x86_64/vdsm/automation/vdsm_functional/default/scripts/_home_jenkins_workspace_vdsm_master_check-merged-el7-x86_64_vdsm_automation_deploy.sh failed with status 1 on vdsm_functional_tests_host-el7
16:20:23 # Deploy environment: ERROR (in 0:00:13)
16:20:23 @ Deploy oVirt environment: ERROR (in 0:00:14)
16:20:23 Error occured, aborting
and
16:21:32 + lago ovirt deploy
16:21:33 current session does not belong to lago group.
16:21:33 @ Deploy oVirt environment:
16:21:33 # ovirt-role metadata entry will be soon deprecated, instead you should use the vm-provider entry in the domain definition and set it no one of: ovirt-node, ovirt-engine, ovirt-host
16:21:33 @ Deploy oVirt environment: ERROR (in 0:00:00)
16:21:33 Error occured, aborting
16:21:33 Traceback (most recent call last):
16:21:33 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 303, in do_run
16:21:33 self.cli_plugins[args.ovirtverb].do_run(args)
16:21:33 File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run
16:21:33 self._do_run(**vars(args))
16:21:33 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 495, in wrapper
16:21:33 return func(*args, **kwargs)
16:21:33 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 506, in wrapper
16:21:33 return func(*args, prefix=prefix, **kwargs)
16:21:33 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 164, in do_deploy
16:21:33 prefix.deploy()
16:21:33 File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 633, in wrapper
16:21:33 return func(*args, **kwargs)
16:21:33 File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 110, in wrapper
16:21:33 with utils.repo_server_context(args[0]):
16:21:33 File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
16:21:33 return self.gen.next()
16:21:33 File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 97, in repo_server_context
16:21:33 root_dir=prefix.paths.internal_repo(),
16:21:33 File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 73, in _create_http_server
16:21:33 generate_request_handler(root_dir),
16:21:33 File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__
16:21:33 self.server_bind()
16:21:33 File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind
16:21:33 SocketServer.TCPServer.server_bind(self)
16:21:33 File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind
16:21:33 self.socket.bind(self.server_address)
16:21:33 File "/usr/lib64/python2.7/socket.py", line 224, in meth
16:21:33 return getattr(self._sock,name)(*args)
16:21:33 error: [Errno 98] Address already in use
Do you know what's wrong?
Thanks,
Milan
7 years, 8 months
oVirt infra daily report - unstable production jobs - 286
by jenkins@jenkins.phx.ovirt.org
------=_Part_419_1305445919.1491778807014
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/286//artifact/exported...
Cheers,
Jenkins
------=_Part_419_1305445919.1491778807014
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 - 09/04/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_3.6_publish-rpms_nightly/">ovirt_3.6_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (3.6 branches) and publish them to resources.ovirt.org yum repository.<br> 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.0_publish-rpms_nightly/">ovirt_4.0_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (4.0 branches) and publish them to resources.ovirt.org yum repository.<br> 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_publish-rpms_nightly/">ovirt_4.1_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (4.1 branches) and publish them to resources.ovirt.org yum repository.<br> 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-ansible-system-tests/">ovirt_master-ansible-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/ovirt_master_publish-rpms_nightly/">ovirt_master_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (master branches) and publish them to resources.ovirt.org yum repository.<br> 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/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</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/test-repo_ovirt_experimental_master-dry_run/">test-repo_ovirt_experimental_master-dry_run</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_419_1305445919.1491778807014--
7 years, 8 months
[JIRA] (OVIRT-1313) Make OST manual job build history more useful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1313:
--------------------------------
Description:
Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
We can also consider adding the name of the person that ran the job.
was:
Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
> Make OST manual job build history more useful
> ---------------------------------------------
>
> Key: OVIRT-1313
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Priority: Low
> Labels: ost
>
> Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
> We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
> We can also consider adding the name of the person that ran the job.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months
[JIRA] (OVIRT-1313) Make OST manual job build history more useful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1313:
--------------------------------
Summary: Make OST manual job build history more useful (was: Make OST manual job buiold history more useful)
> Make OST manual job build history more useful
> ---------------------------------------------
>
> Key: OVIRT-1313
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Priority: Low
> Labels: ost
>
> Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
> We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months
[JIRA] (OVIRT-1313) Make OST manual job buiold history more useful
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1313:
-----------------------------------
Summary: Make OST manual job buiold history more useful
Key: OVIRT-1313
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins
Reporter: Barak Korren
Assignee: infra
Priority: Low
Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months
[JIRA] (OVIRT-1313) Make OST manual job buiold history more useful
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1313?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1313:
--------------------------------
Epic Link: OVIRT-400
> Make OST manual job buiold history more useful
> ----------------------------------------------
>
> Key: OVIRT-1313
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1313
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Priority: Low
> Labels: ost
>
> Looking at the OST manual job build history is pretty useless right now because seeing a failed build tells you nothing about what actually failed to run.
> We should use the groovy post-build plugin to add information such as the suite type that was run, the oVirt version that was tested and wither custom settings were used.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months