[JIRA] (OVIRT-1005) Fix race condition caused by experimental cleanup script
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1005:
-----------------------------------
Summary: Fix race condition caused by experimental cleanup script
Key: OVIRT-1005
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1005
Project: oVirt - virtualization made easy
Issue Type: Improvement
Reporter: Barak Korren
Assignee: infra
Priority: Highest
The experimental repo has a cleanup script that is ran every hour via cron. The script is meant to delete old and unused package builds.
The content of the script is as follows:
{code}
find \
/srv/resources/repos/ovirt/experimental/*/* \
-maxdepth 0 \
-type d \
-not -name 'latest.*' \
-and \
-mtime +1 \
-exec rm -rf {} \;
{code}
The problem here is that 'latest' is not filtered out to not be deleted by this script. It is OK to delete it in most cases because then it gets recreated by the 'deploy-to-experimental' job, but there might be a case where 'test-repo_ovirt-experimental_*' can run before this happens, this may cause it to get an empty or partial 'latest' repo.
To remedy this, the script needs to be changed to be the following:
{code}
find \
/srv/resources/repos/ovirt/experimental/*/* \
-maxdepth 0 \
-type d \
-not -name 'latest.*' \
-and \
-not -name 'latest' \
-and \
-mtime +1 \
-exec rm -rf {} \;
{code}
The script itself on the resources server was already changed in-palce, this ticket is so we this change is also "backed up" to the 'infra-puppet' repo.
--
This message was sent by Atlassian JIRA
(v1000.656.2#100024)
7 years, 10 months
[JIRA] (OVIRT-1005) Fix race condition caused by experimental cleanup script
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1005?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1005:
--------------------------------
Epic Link: OVIRT-400
> Fix race condition caused by experimental cleanup script
> --------------------------------------------------------
>
> Key: OVIRT-1005
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1005
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Barak Korren
> Assignee: infra
> Priority: Highest
>
> The experimental repo has a cleanup script that is ran every hour via cron. The script is meant to delete old and unused package builds.
> The content of the script is as follows:
> {code}
> find \
> /srv/resources/repos/ovirt/experimental/*/* \
> -maxdepth 0 \
> -type d \
> -not -name 'latest.*' \
> -and \
> -mtime +1 \
> -exec rm -rf {} \;
> {code}
> The problem here is that 'latest' is not filtered out to not be deleted by this script. It is OK to delete it in most cases because then it gets recreated by the 'deploy-to-experimental' job, but there might be a case where 'test-repo_ovirt-experimental_*' can run before this happens, this may cause it to get an empty or partial 'latest' repo.
> To remedy this, the script needs to be changed to be the following:
> {code}
> find \
> /srv/resources/repos/ovirt/experimental/*/* \
> -maxdepth 0 \
> -type d \
> -not -name 'latest.*' \
> -and \
> -not -name 'latest' \
> -and \
> -mtime +1 \
> -exec rm -rf {} \;
> {code}
> The script itself on the resources server was already changed in-palce, this ticket is so we this change is also "backed up" to the 'infra-puppet' repo.
--
This message was sent by Atlassian JIRA
(v1000.656.2#100024)
7 years, 10 months
engine CI failing upgrade tasks due to missing dependencies
by Allon Mureinik
Hi infra,
Upgrade tasks in engine CI seem to be failing due to missing dependencies.
E.g. [1]:
Error downloading packages:
vdsm-jsonrpc-java-1.3.5-1.20170103113616.gitfbe3dec.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-dwh-setup-4.1.0-0.0.master.20170103090346.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-dwh-4.1.0-0.0.master.20170103090346.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-cli-3.6.9.3-0.1.20170103.git61c5da9.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-imageio-proxy-1.0.0-0.201701021040.git022783e.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-sdk-python-3.6.9.2-0.1.20170103.gite99bbd1.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-imageio-proxy-setup-1.0.0-0.201701021040.git022783e.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-extension-aaa-jdbc-1.1.3-0.0.master.20170103103520.gitd0ff686.el7.noarch:
[Errno 256] No more mirrors to try.
ovirt-vmconsole-proxy-1.0.4-0.0.master.20170103150743.git51ed572.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-vmconsole-1.0.4-0.0.master.20170103150743.git51ed572.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-iso-uploader-4.1.0-0.0.master.20170103091034.git14502bd.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-setup-lib-1.1.0-1.20170103120007.git402fec4.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-host-deploy-1.6.0-0.0.master.20170103133827.git7eea7f1.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-host-deploy-java-1.6.0-0.0.master.20170103133827.git7eea7f1.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch: [Errno 256] No
more mirrors to try.
ovirt-engine-dashboard-1.1.0-0.4.20170103gitfad882b.el7.centos.noarch:
[Errno 256] No more mirrors to try.
ovirt-imageio-common-1.0.0-0.201701021040.git022783e.el7.centos.noarch:
[Errno 256] No more mirrors to try.
[1]
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_cre...
7 years, 10 months
oVirt infra daily report - unstable production jobs - 189
by jenkins@jenkins.phx.ovirt.org
------=_Part_91_1455951705.1483484462352
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/189//artifact/exported...
Cheers,
Jenkins
------=_Part_91_1455951705.1483484462352
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 - 03/01/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/deploy-to-ovirt_experimental_3.6/">deploy-to-ovirt_experimental_3.6</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-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</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_3.6_he-system-tests/">ovirt_3.6_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_3.6_image-ng-system-tests/">ovirt_3.6_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.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_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_fc24_merged/">repos_master_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/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</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_91_1455951705.1483484462352--
7 years, 10 months
[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Juan Hernández (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jir... ]
Juan Hernández commented on OVIRT-1000:
---------------------------------------
Not sure what you mean by "where they should be built"? Do you mean for what versions of oVirt they should be built? In that case this is my suggestion:
Git repository - RPM name - Where to build
ovirt-engine-sdk - python-ovirt-engine-sdk4 - 4.y
ovirt-engine-sdk-java - java-ovirt-engine-sdk4 - 4.y
ovirt-engine-sdk-v3 - ovirt-engine-sdk-python - 3.y and 4.y
ovirt-engine-sdk-java-v3 - ovirt-engine-sdk-java - 3.y and 4.y
Would that help? I mean, doing this isn't useful for me, I am suggesting it because I thought it would solve the issues that you experience in the CI environment. Maybe we should setup a meeting so that you can explain me better what are those issues.
> Java SDK 4.1 branch don't execute jenkins jobs
> ----------------------------------------------
>
> Key: OVIRT-1000
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
> Reporter: Ondra Machacek
> Assignee: infra
>
> Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project,
> you can see an example here: https://gerrit.ovirt.org/#/c/69455/1
> I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job.
> [1] https://gerrit.ovirt.org/#/c/69459/
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 10 months