- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5506 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '17

23 Feb '17

------=_Part_355_498714304.1487877973254 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5506/, Build Number: 5506, Build Status: FAILURE ------=_Part_355_498714304.1487877973254--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3829 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '17

23 Feb '17

------=_Part_353_838379894.1487876899184 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3829/, Build Number: 3829, Build Status: FAILURE ------=_Part_353_838379894.1487876899184--

1 1

[ OST Failure Report ] [ oVirt master ] [ 22/02/2017 ] [add_secondary_storage_domains]
by Barak Korren 23 Feb '17

23 Feb '17

Test failed: [ add_secondary_storage_domains ] Note: - This may or may not be related to https://bugzilla.redhat.com/show_bug.cgi?id=1421945 The BZ talks about sporadic failures, while this seems to be happening consistently (for 6 runs so far) Link to suspected patches: - https://gerrit.ovirt.org/70415 - https://gerrit.ovirt.org/69157 Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/artif… Error snippet from log: <error> RequestError: status: 400 reason: Bad Request detail: Cannot import Virtual Disk: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. </error> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/testR… -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

4 13

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5487 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '17

23 Feb '17

------=_Part_311_872300055.1487798669441 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/, Build Number: 5487, Build Status: FAILURE ------=_Part_311_872300055.1487798669441--

1 17

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #97
by jenkins＠jenkins.phx.ovirt.org 23 Feb '17

23 Feb '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/97/display…> ------------------------------------------ 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 d735e178b27457ed4022a9fdcd42d0b9de722a91 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d735e178b27457ed4022a9fdcd42d0b9de722a91 > git rev-list d735e178b27457ed4022a9fdcd42d0b9de722a91 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson1143467619224303592.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc25/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1194) Gerrit maintenance tasks February 2017
by Evgheni Dereveanchin (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1194?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1194: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Gerrit maintenance tasks February 2017 > -------------------------------------- > > Key: OVIRT-1194 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1194 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Tracker for pending Gerrit maintenance and updates. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1194) Gerrit maintenance tasks February 2017
by Evgheni Dereveanchin (oVirt JIRA) 23 Feb '17

23 Feb '17

Evgheni Dereveanchin created OVIRT-1194: ------------------------------------------- Summary: Gerrit maintenance tasks February 2017 Key: OVIRT-1194 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1194 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Tracker for pending Gerrit maintenance and updates. -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1193) Re: Howto message for every gerrit review
by Martin Sivak (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.… ] Martin Sivak commented on OVIRT-1193: ------------------------------------- > This is doable, but I think experienced users may find this annoying > it ifs too long. > > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. It does not have to be long, just a summary of all the links once when the change is posted (so the links can contain the proper change id and jenkins links). I am actually more annoyed by the fact that I have to look for the information. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). That would be even better > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. That might work too, but I feel a bot sending a message is faster and easier to do. Martin On Thu, Feb 23, 2017 at 2:18 PM, Barak Korren <bkorren(a)redhat.com> wrote: > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: >> Hi, >> >> do you think it would make sense to send a copy-and-paste ready >> message with help to every new gerrit change? >> >> It could provide all the system test (lago) links, mention the Rerun >> hooks syntax and so on. Just so we do not have to search for it all >> the time? > > This is doable, but I think experienced users may find this annoying > it ifs too long. > > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > > Adding infra-support to get a Jira ticket opened. > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ > Re: Howto message for every gerrit review > ----------------------------------------- > > Key: OVIRT-1193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > > do you think it would make sense to send a copy-and-paste ready > > message with help to every new gerrit change? > > > > It could provide all the system test (lago) links, mention the Rerun > > hooks syntax and so on. Just so we do not have to search for it all > > the time? > This is doable, but I think experienced users may find this annoying > it ifs too long. > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > Adding infra-support to get a Jira ticket opened. > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1193) Re: Howto message for every gerrit review
by Barak Korren (oVirt JIRA) 23 Feb '17

23 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1193: -------------------------------- Component/s: Gerrit/git > Re: Howto message for every gerrit review > ----------------------------------------- > > Key: OVIRT-1193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > > do you think it would make sense to send a copy-and-paste ready > > message with help to every new gerrit change? > > > > It could provide all the system test (lago) links, mention the Rerun > > hooks syntax and so on. Just so we do not have to search for it all > > the time? > This is doable, but I think experienced users may find this annoying > it ifs too long. > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > Adding infra-support to get a Jira ticket opened. > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0

[JIRA] (OVIRT-1193) Re: Howto message for every gerrit review
by Barak Korren (oVirt JIRA) 23 Feb '17

23 Feb '17

Barak Korren created OVIRT-1193: ----------------------------------- Summary: Re: Howto message for every gerrit review Key: OVIRT-1193 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > Hi, > > do you think it would make sense to send a copy-and-paste ready > message with help to every new gerrit change? > > It could provide all the system test (lago) links, mention the Rerun > hooks syntax and so on. Just so we do not have to search for it all > the time? This is doable, but I think experienced users may find this annoying it ifs too long. I'm thinking it may be better to have such a message just suggesting to type something like '@ci help' to get the full help. It may even be possible to make it clickable with some trickery rather then just copy-and-paster ready (I will need to check if its possible to inject links into Gerrit comments). Apart from that, Roy offered to write a Gerrit plugin that will add buttons with the various CI commands. Adding infra-support to get a Jira ticket opened. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.773.3#100032)

1 0