- Infra - oVirt List Archives

[CQ]: 106090, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106090,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106090/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2804/

1 0

[JIRA] (OVIRT-2856) Requesting merge rights to ovirt-engine-sdk-ruby
by Shlomi Zidmi (oVirt JIRA) 15 Jan '20

15 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2856?page=com.atlassian.jira.… ] Shlomi Zidmi updated OVIRT-2856: -------------------------------- Assignee: Shlomi Zidmi (was: infra) Resolution: Done Status: Done (was: To Do) Done > Requesting merge rights to ovirt-engine-sdk-ruby > ------------------------------------------------ > > Key: OVIRT-2856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2856 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ori Liel > Assignee: Shlomi Zidmi > > I need merge (+2) rights to ovirt-engine-sdk-ruby, as I am becoming a maintainer of this project. > This request is approved by my manager Martin Perina and the existing maintainers of this project, Ondra Machacek and Boris Odnopozov -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[CQ]: 106088, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106088,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106088/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2801/

1 0

[CQ]: 105989, 26 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-master" change queue including change 105989,26 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106134,5 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106134,5 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/105989/26 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106134/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18038/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #125 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Jan '20

15 Jan '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/125/ Build Name: #125 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 3

[CQ]: 105987, 25 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-master" change queue including change 105987,25 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106134,5 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106134,5 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/105987/25 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106134/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18031/

1 0

[CQ]: 106089, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106089,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106089/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2799/

1 0

[CQ]: 106087, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '20

15 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106087,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106087/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2797/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #180 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Jan '20

15 Jan '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/180/ Build Name: #180 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1070
by jenkins＠jenkins.phx.ovirt.org 15 Jan '20

15 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1070//artifact/exported… Cheers, Jenkins

1 0

planned Jenkins restart
by Evgheni Dereveanchin 14 Jan '20

14 Jan '20

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

[CQ]: 106086, 3 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '20

14 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106086,3 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106086/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2795/

1 0

[CQ]: 106258, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '20

14 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106258,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106134,5 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106134,5 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106258/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106134/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18027/

1 0

[CQ]: 106298, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '20

14 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106298,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106120,5 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106298/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2794/

1 0

[CQ]: 106120, 5 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 106120,5 (ovirt-system-tests) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18021/

1 0

Missing e-mail notifications from gerrit about review requests
by Milan Zamazal 14 Jan '20

14 Jan '20

Hi, it seems gerrit doesn't send e-mail notifications to reviewers when they are added as reviewers to patches. For example, I haven't received an e-mail notification about being added as a reviewer to https://gerrit.ovirt.org/106310 and https://gerrit.ovirt.org/106311 today. I have heard from Tomasz that he has this problem for a couple of last days (at least since Friday) too. Other e-mail notifications from gerrit seem to come normally. Could you please check what's wrong? Thanks, Milan

1 0

[CQ]: 105979,5 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 105979,5 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105979/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18014/

1 0

[JIRA] (OVIRT-2857) zone transfer to OSAS dns broken from PHX
by Evgheni Dereveanchin (oVirt JIRA) 14 Jan '20

14 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2857?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2857: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > zone transfer to OSAS dns broken from PHX > ----------------------------------------- > > Key: OVIRT-2857 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2857 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Marc Dequènes (Duck) > > I've been experiencing issues with hostnames showing outdated IPs recently in PHX. > Looks like zone transfer is broken between foreman.phx.ovirt.org and OSAS DNS servers, specifically ns1.osci.io and ns2.osci.io that are mentioned as authoritative for this zone. > Example: > dig staging-shift-int.phx.ovirt.org @foreman.phx.ovirt.org > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 38.145.50.70 > dig staging-shift-int.phx.ovirt.org @ns1.osci.io > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 > dig staging-shift-int.phx.ovirt.org @ns2.osci.io > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 > The correct IP is 38.145.50.70 in this case and the name server in PHX has already been restarted and re-transfer initiated several times yet unfortunately the changes are not visible on OSAS DNS which is blocking us from rebuilding the staging OpenShift environment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2857) zone transfer to OSAS dns broken from PHX
by Evgheni Dereveanchin (oVirt JIRA) 14 Jan '20

14 Jan '20

Evgheni Dereveanchin created OVIRT-2857: ------------------------------------------- Summary: zone transfer to OSAS dns broken from PHX Key: OVIRT-2857 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2857 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I've been experiencing issues with hostnames showing outdated IPs recently in PHX. Looks like zone transfer is broken between foreman.phx.ovirt.org and OSAS DNS servers, specifically ns1.osci.io and ns2.osci.io that are mentioned as authoritative for this zone. Example: dig staging-shift-int.phx.ovirt.org @foreman.phx.ovirt.org ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 38.145.50.70 dig staging-shift-int.phx.ovirt.org @ns1.osci.io ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 dig staging-shift-int.phx.ovirt.org @ns2.osci.io ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 The correct IP is 38.145.50.70 in this case and the name server in PHX has already been restarted and re-transfer initiated several times yet unfortunately the changes are not visible on OSAS DNS which is blocking us from rebuilding the staging OpenShift environment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2856) Requesting merge rights to ovirt-engine-sdk-ruby
by Ori Liel (oVirt JIRA) 14 Jan '20

14 Jan '20

Ori Liel created OVIRT-2856: ------------------------------- Summary: Requesting merge rights to ovirt-engine-sdk-ruby Key: OVIRT-2856 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2856 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ori Liel Assignee: infra I need merge (+2) rights to ovirt-engine-sdk-ruby, as I am becoming a maintainer of this project. This request is approved by my manager Martin Perina and the existing maintainers of this project, Ondra Machacek and Boris Odnopozov -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[CQ]: 106120,5 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 106120,5 (ovirt-system-tests) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2792/

1 0

[CQ]: 105975,5 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 105975,5 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105975/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18012/

1 0

[CQ]: 106134,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 106134,5 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106134/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18004/

1 0

oVirt infra daily report - unstable production jobs - 1069
by jenkins＠jenkins.phx.ovirt.org 14 Jan '20

14 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1069//artifact/exported… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #167
by jenkins＠jenkins.phx.ovirt.org 13 Jan '20

13 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/167/…> Changes: ------------------------------------------ Started by user Shlomi Zidmi Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/ws/> No credentials specified > 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 No valid HEAD. Skipping the resetting > 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 --prune http://gerrit.ovirt.org/jenkins.git +refs/head/myhead:refs/changes/18/106118/2 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/head/myhead:refs/changes/18/106118/2" returned status code 128: stdout: stderr: fatal: Couldn't find remote ref refs/head/myhead Unexpected end of command stream at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mirrors.phx.ovirt.org at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor655.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy98.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) ERROR: Error fetching remote repo 'origin'

1 3

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #165
by jenkins＠jenkins.phx.ovirt.org 13 Jan '20

13 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/165/…> Changes: ------------------------------------------ Started by user Shlomi Zidmi Rebuilds build #164 Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/ws/> No credentials specified Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/ws/j…> # timeout=10 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/* > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/changes/18/106118/2^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/changes/18/106118/2^{commit} # timeout=10 > git rev-parse refs/changes/18/106118/2^{commit} # timeout=10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

1 1

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #163
by jenkins＠jenkins.phx.ovirt.org 13 Jan '20

13 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/163/…> Changes: ------------------------------------------ Started by user Shlomi Zidmi Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/ws/> No credentials specified > 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 --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/changes/18/106118/2^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/changes/18/106118/2^{commit} # timeout=10 > git rev-parse refs/changes/18/106118/2^{commit} # timeout=10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

1 1

[CQ]: 106249,1 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 13 Jan '20

13 Jan '20

Change 106249,1 (ovirt-system-tests) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106249/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2783/

1 0

[JIRA] (OVIRT-2855) Requesting merge rights to ovirt-engine-sdk-java
by Ehud Yonasi (oVirt JIRA) 13 Jan '20

13 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2855?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2855: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Requesting merge rights to ovirt-engine-sdk-java > ------------------------------------------------ > > Key: OVIRT-2855 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2855 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ori Liel > Assignee: Ehud Yonasi > Priority: High > > Hi, > I am going to be maintaining ovirt-engine-sdk-java and I need merge rights for this project. > Approved by my manager, Martin Perina and by the existing maintainer, Ondra Machacek > thank you, > Ori -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2855) Requesting merge rights to ovirt-engine-sdk-java
by Ori Liel (oVirt JIRA) 13 Jan '20

13 Jan '20

Ori Liel created OVIRT-2855: ------------------------------- Summary: Requesting merge rights to ovirt-engine-sdk-java Key: OVIRT-2855 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2855 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ori Liel Assignee: infra Priority: High Hi, I am going to be maintaining ovirt-engine-sdk-java and I need merge rights for this project. Approved by my manager, Martin Perina and by the existing maintainer, Ondra Machacek thank you, Ori -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

oVirt infra daily report - unstable production jobs - 1068
by jenkins＠jenkins.phx.ovirt.org 13 Jan '20

13 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1068//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 80205cd (wix-toolset-binaries) failed "ovirt-master" system tests
by oVirt Jenkins 12 Jan '20

12 Jan '20

Change 80205cd (wix-toolset-binaries) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/wix-toolset-binaries/commit/80205cd2ea115eaf40c5a6… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17982/

1 0

oVirt infra daily report - unstable production jobs - 1067
by jenkins＠jenkins.phx.ovirt.org 12 Jan '20

12 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1067//artifact/exported… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 1066
by jenkins＠jenkins.phx.ovirt.org 11 Jan '20

11 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1066//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 84869,2 (ovirt-optimizer) failed "ovirt-master" system tests
by oVirt Jenkins 10 Jan '20

10 Jan '20

Change 84869,2 (ovirt-optimizer) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/84869/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17975/

1 0

[CQ]: 106218,1 (ovirt-release) failed "ovirt-master" system tests
by oVirt Jenkins 10 Jan '20

10 Jan '20

Change 106218,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106218/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17973/

1 0

[JIRA] (OVIRT-2854) artifactory.ovirt.org SSL certificate expired June 26th, 2019.
by Sandro Bonazzola (oVirt JIRA) 10 Jan '20

10 Jan '20

Sandro Bonazzola created OVIRT-2854: --------------------------------------- Summary: artifactory.ovirt.org SSL certificate expired June 26th, 2019. Key: OVIRT-2854 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2854 Project: oVirt - virtualization made easy Issue Type: Outage Components: Repositories Mgmt Reporter: Sandro Bonazzola Assignee: infra Priority: High artifactory.ovirt.org SSL certificate expired June 26th, 2019. since http now redirects to https, we need the certificate to be updated. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[CQ]: 105491, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 10 Jan '20

10 Jan '20

Change 105491,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105491/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17972/

1 0

[CQ]: 105491, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Jan '20

10 Jan '20

Change 105491,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105491/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2775/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #236
by jenkins＠jenkins.phx.ovirt.org 10 Jan '20

10 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> No credentials specified > 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 --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9ad7dff1d96ad50a54d021d167c842cbffe7d014 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9ad7dff1d96ad50a54d021d167c842cbffe7d014 Commit message: "gate: Move test suit to use DSL & container" > git rev-list --no-walk 9ad7dff1d96ad50a54d021d167c842cbffe7d014 # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1019101500430693589.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-sclo-rh-release-7.6-el7 yum + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7 /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base + check_yum_sync_needed centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-sclo-rh-release-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-7.6-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-7.6-el7/gen' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 1065
by jenkins＠jenkins.phx.ovirt.org 10 Jan '20

10 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1065//artifact/exported… Cheers, Jenkins

1 0

[CQ]: baf4505 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 09 Jan '20

09 Jan '20

Change baf4505 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/baf4505295a15a79ca9b83411d9a0b… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17967/

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ for infra issue i am not certain, we need to ask Evgheni maybe. because 2 runs produced the same results. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ so if it’s only decided in the stage itself, I think that’s safe enough to limit for 5h. you can’t alter it on runtime.. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Dusan Fodor (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Dusan Fodor edited comment on OVIRT-2853 at 1/9/20 8:59 AM: ------------------------------------------------------------ Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been an infra issue. was (Author: dfodor): Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been in infra issue. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Dusan Fodor (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Dusan Fodor commented on OVIRT-2853: ------------------------------------ Then we would have the same 5hrs timeout for all the builds (even the non release ones, which have less permutation and take less time), so i'm not sure that good enough solution. Extending the timeout only for the release build only would be better, but it is only decided in build_artifacts.sh how many permutation will it do, so already below level of stages. Also, i don't remember seeing this before, so it might've been in infra issue. > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2853) ovirt-engine standard checkpatch times out when doing release build
by Ehud Yonasi (oVirt JIRA) 09 Jan '20

09 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2853?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2853: ------------------------------------ You can define stages in the stdci.yaml file and under the build-artifacts stage you can define: timeout: 5h > ovirt-engine standard checkpatch times out when doing release build > ------------------------------------------------------------------- > > Key: OVIRT-2853 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2853 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > Labels: infra > > Link to the job: > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine_standard-… > It failed on timeout (3hrs), but the job it triggered [1] finished successfully (in 5+hrs though). This is special case of release build which builds all possible permutations-option BUILD_GWT is enabled in [2]. > [1] https://jenkins.ovirt.org/job/ovirt-engine_4.3_check-patch-el7-x86_64/649/ > [2] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/chec… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #233
by jenkins＠jenkins.phx.ovirt.org 09 Jan '20

09 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> No credentials specified > 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 --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9ad7dff1d96ad50a54d021d167c842cbffe7d014 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9ad7dff1d96ad50a54d021d167c842cbffe7d014 Commit message: "gate: Move test suit to use DSL & container" > git rev-list --no-walk 9ad7dff1d96ad50a54d021d167c842cbffe7d014 # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5525763586160551627.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-sclo-rh-release-7.6-el7 yum + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7 /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base + check_yum_sync_needed centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-sclo-rh-release-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 1064
by jenkins＠jenkins.phx.ovirt.org 09 Jan '20

09 Jan '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1064//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 106097,1 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 08 Jan '20

08 Jan '20

Change 106097,1 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106097/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17957/

1 0