January 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1063) Experimental flow artifacts are collected differently of the flow succeeds or fails

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1063: ----------------------------------- Summary: Experimental flow artifacts are collected differently of the flow succeeds or fails Key: OVIRT-1063 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1063 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra There is a bug in the experimental pipeline Groovy scripts that makes the artifact collection code run in a different directory if the job fails or succeeds. This is probably making debugging harder then it should be. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1063) Experimental flow artifacts are collected differently of the flow succeeds or fails

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1063?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1063: -------------------------------- Epic Link: OVIRT-400 > Experimental flow artifacts are collected differently of the flow succeeds or fails > ----------------------------------------------------------------------------------- > > Key: OVIRT-1063 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1063 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > There is a bug in the experimental pipeline Groovy scripts that makes the artifact collection code run in a different directory if the job fails or succeeds. > This is probably making debugging harder then it should be. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1022) Files are read only after STD-CI jobs run

by Gil Shinar (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1022?page=com.atlassian.jir... ] Gil Shinar updated OVIRT-1022: ------------------------------ Resolution: Fixed Status: Done (was: To Do) > Files are read only after STD-CI jobs run > ----------------------------------------- > > Key: OVIRT-1022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > Priority: Highest > > Some check-patch, check-merged, build-artifacts scripts makes changes to files' permissions. > I have added fix for that in cleanup slave phase -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1022) Files are read only after STD-CI jobs run

by Gil Shinar (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1022?page=com.atlassian.jir... ] Gil Shinar commented on OVIRT-1022: ----------------------------------- Yup Sorry for not updating: https://gerrit.ovirt.org/#/c/70042/ > Files are read only after STD-CI jobs run > ----------------------------------------- > > Key: OVIRT-1022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > Priority: Highest > > Some check-patch, check-merged, build-artifacts scripts makes changes to files' permissions. > I have added fix for that in cleanup slave phase -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1062) Make sure Atomic images are up to date in glance.

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1062?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-1062: ----------------------------------- Assignee: Barak Korren (was: infra) > Make sure Atomic images are up to date in glance. > ------------------------------------------------- > > Key: OVIRT-1062 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1062 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > > It seems we're not getting any updates to the Atomic images in our Glance despite new releases: > http://www.projectatomic.io/blog/2017/01/centos-atomic-jan17/ > It seems this is because the naming scheme for atomic image files was changed so our updating code no longer works. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1062) Make sure Atomic images are up to date in glance.

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1062?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1062: -------------------------------- Issue Type: Bug (was: Improvement) > Make sure Atomic images are up to date in glance. > ------------------------------------------------- > > Key: OVIRT-1062 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1062 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > It seems we're not getting any updates to the Atomic images in our Glance despite new releases: > http://www.projectatomic.io/blog/2017/01/centos-atomic-jan17/ > It seems this is because the naming scheme for atomic image files was changed so our updating code no longer works. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1062) Make sure Atomic images are up to date in glance.

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1062?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1062: -------------------------------- Epic Link: OVIRT-403 > Make sure Atomic images are up to date in glance. > ------------------------------------------------- > > Key: OVIRT-1062 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1062 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > It seems we're not getting any updates to the Atomic images in our Glance despite new releases: > http://www.projectatomic.io/blog/2017/01/centos-atomic-jan17/ > It seems this is because the naming scheme for atomic image files was changed so our updating code no longer works. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1062) Make sure Atomic images are up to date in glance.

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1062: ----------------------------------- Summary: Make sure Atomic images are up to date in glance. Key: OVIRT-1062 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1062 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra It seems we're not getting any updates to the Atomic images in our Glance despite new releases: http://www.projectatomic.io/blog/2017/01/centos-atomic-jan17/ It seems this is because the naming scheme for atomic image files was changed so our updating code no longer works. -- This message was sent by Atlassian JIRA (v1000.695.3#100025)

7 years, 10 months

1
0
0 / 0

New image releases and image file names

by Barak Korren

Hi there, In the oVirt projects we're making some efforts to make it easy to get stuff up and running on top of oVirt. One of these efforts is maintaining a Glance server containing updated "cloud" VM images of various distros including, among others, Fedora, CentOS, Ubuntu and Atomic. That Glance server is configured for use by default in all oVirt installations. Since upstream images can update quite often, we've made efforts to automate the process of polling the disro download servers for new images, and downloading them into Glance. In order to make images useful for users, we need to know various details like which OS version is in the image. Since every distro has got its own idea about how to organise the download server and name the files in it, we had to resort to regex-matching the image files to extract useful details about them. This is why its very frustrating to us when an upstream changes the way it names its image files. Especially when the files are named in a way that prevents keeping an orderly image archive. As a new CentOS Atomic image was recently released [1], we set about to getting that image uploaded to our Glance server. We found out the name of the new image file seems to be very different from how Atomic images used to be called. If seems the new image is called simply: CentOS-Atomic-Host-7-GenericCloud.qcow2 This is while older images were called something like: CentOS-Atomic-Host-7.1609-GenericCloud.qcow2 The newer name is useless as far as image version tracking goes. We would like to request that the new naming scheme would be restored, or at least some other scheme is created where its easy to automatically figure out the image versions. [1]: http://www.projectatomic.io/blog/2017/01/centos-atomic-jan17/ Thanks, -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

7 years, 10 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 207

by jenkins＠jenkins.phx.ovirt.org

------=_Part_7_1009091204.1485039610088 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/207//artifact/exported... Cheers, Jenkins ------=_Part_7_1009091204.1485039610088 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 - 21/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/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.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-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.  </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.  </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.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_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.  </td></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.  </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.  </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.  </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.  </td></tr> ------=_Part_7_1009091204.1485039610088--

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra January 2017