- Infra - oVirt List Archives

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #607
by jenkins＠jenkins.phx.ovirt.org 17 May '19

17 May '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/607/display/red…>

1 1

[CQ]: 98601,11 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 17 May '19

17 May '19

Change 98601,11 (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/98601/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14159/

1 0

oVirt infra daily report - unstable production jobs - 827
by jenkins＠jenkins.phx.ovirt.org 17 May '19

17 May '19

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/827//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99893, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 May '19

17 May '19

A system test invoked by the "ovirt-master" change queue including change 99893,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/99893/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14155/

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Barak Korren (oVirt JIRA) 17 May '19

17 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2730: ------------------------------------- On Wed, 15 May 2019 at 18:58, Nir Soffer (oVirt JIRA) < Looking at the stdci.yaml file I get when cloning the patch - I don't see any substages or distroes defined in it, so STDCI does what it can in that case - run the default substage for the specified architectures that it can find script files for. Is this based on a very old version of vdsm's stdci.yaml ? You can see the exact same thing happening for check-patch triggered from Gerrit: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… In fact running check-patch with manual runner is quite useless, since CI will always run it for you anyway when you push the patch... Because you can't select substages like that. check-network would not work since its not defined in stdci.yaml for that patch. It runs the exact same code. - allow selection of a sub stage? Probably not gonna happen - this would require some deep changes. - nice to have - allow selection of multiple sub stages Same as above, you can only select a stage at this point. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

2 1

[CQ]: 99706, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 99706,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/99706/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14154/

1 0

[CQ]: 99805, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 99805,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/99805/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14152/

1 0

[CQ]: 100093, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 16 May '19

16 May '19

A system test invoked by the "ovirt-master" change queue including change 100093,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99372,6 (ovirt-engine) 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 99372,6 (ovirt-engine) 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/100093/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14151/

1 0

[CQ]: 100111,1 (ovirt-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100111,1 (ovirt-host) 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/100111/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/905/

1 0

[CQ]: 99372,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 99372,6 (ovirt-engine) 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/99372/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14148/

1 0

[CQ]: 100083,1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100083,1 (ovirt-node-ng-image) 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/100083/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/897/

1 0

adding myself to CI whitelist
by Liran Rotenberg 16 May '19

16 May '19

Hi, I would like to add myself to the CI whitelist. I need it in order to build CI and check my patch for example: https://gerrit.ovirt.org/#/c/99970/ Thanks, Liran.

3 3

[CQ]: 100067, 1 (ovirt-engine-api-explorer) failed "ovirt-4.3" system tests
by oVirt Jenkins 16 May '19

16 May '19

Change 100067,1 (ovirt-engine-api-explorer) 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/100067/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/896/

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer (oVirt JIRA) 16 May '19

16 May '19

Nir Soffer created OVIRT-2730: --------------------------------- Summary: Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ Key: OVIRT-2730 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I tried to run check-patch and check-patch linters substage from the command line: using: https://github.com/nirs/oci/pull/37 I assumed that this will run the entire check-patch stage, including all the sub stages: ./ovirt-ci run -s check-patch 100007 But it run something that looks like check-patch with el7: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… The test environment seems to be different that what we have when check-patch is triggered from gerrit. Then I tried to run the linters substage: ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… ./ovirt-ci run -s check-patch.linters 100007 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Both succeeded without running anything :-) Running build-artifacts works, not sure about check-network. Can we fix the manual job so: - it run exactly the same way as it run when gerrit trigger the job - allow selection of a sub stage? - nice to have - allow selection of multiple sub stages Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

2 1

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 579 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 May '19

16 May '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/579/ Build Number: 579 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #579 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 826
by jenkins＠jenkins.phx.ovirt.org 16 May '19

16 May '19

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/826//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100050, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 15 May '19

15 May '19

Change 100050,1 (ovirt-engine-metrics) 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/100050/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14130/

1 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/
by Nir Soffer (oVirt JIRA) 15 May '19

15 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2730: ----------------------------------- On Wed, May 15, 2019 at 6:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I tried to run check-patch and check-patch linters substage from the > command line: > > using: > https://github.com/nirs/oci/pull/37 > > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > > But it run something that looks like check-patch with el7: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > For reference, I started only this build, from Jenkins UI: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Which seem to the same thing. > > Then I tried to run the linters substage: > > ./ovirt-ci run -s check-patch.linters 100007 > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > ./ovirt-ci run -s check-patch.linters 100007 > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > Both succeeded without running anything :-) > > Running build-artifacts works, not sure about check-network. > > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > > Nir > > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[CQ]: 3ea7a2a (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests
by oVirt Jenkins 15 May '19

15 May '19

Change 3ea7a2a (ovirt-ansible-vm-infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/3ea7a2a576d7e4413123… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/888/

1 0

[JIRA] (OVIRT-2729) patch infra against MDS vulnerabilities
by Evgheni Dereveanchin (oVirt JIRA) 15 May '19

15 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2729?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2729: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > patch infra against MDS vulnerabilities > --------------------------------------- > > Key: OVIRT-2729 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2729 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Several more meltdown-like vulnerabilities have been disclosed: > https://access.redhat.com/security/vulnerabilities/mds > For RHEL the fixed versions seem to be: > kernel-3.10.0-957.12.2 > kernel-2.6.32-754.14.2 > Need to wait till these versions are available for CentOS and the fix is out for fedora to patch our systems -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2729) patch infra against MDS vulnerabilities
by Evgheni Dereveanchin (oVirt JIRA) 15 May '19

15 May '19

Evgheni Dereveanchin created OVIRT-2729: ------------------------------------------- Summary: patch infra against MDS vulnerabilities Key: OVIRT-2729 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2729 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Several more meltdown-like vulnerabilities have been disclosed: https://access.redhat.com/security/vulnerabilities/mds For RHEL the fixed versions seem to be: kernel-3.10.0-957.12.2 kernel-2.6.32-754.14.2 Need to wait till these versions are available for CentOS and the fix is out for fedora to patch our systems -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[CQ]: f1ab12e (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 15 May '19

15 May '19

Change f1ab12e (ovirt-ansible-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" 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-ansible-engine-setup/commit/f1ab12efb623109c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4357/

1 0

[JIRA] (OVIRT-2728) Old emails resurfacing
by Eyal Edri (oVirt JIRA) 15 May '19

15 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2728?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2728: -------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) Hi [~duck], Can you have a look? it might related to recent changes/upgrades done on the ML? cc [~ederevea][~misc(a)redhat.com] in case Duck isn't around. > Old emails resurfacing > ---------------------- > > Key: OVIRT-2728 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2728 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Benny Zlotnik > Assignee: Marc Dequènes (Duck) > > Hi, > Public lists, especially users@ovirt, have a large amount of emails > from 2016 resurfacing[1] > This pushes down actual new and relevant emails from users, also some > new emails don't reach my inbox[2] > [1] - https://lists.ovirt.org/archives/list/users@ovirt.org/thread/BW5EV5PFIXRBT6… > [2] - https://lists.ovirt.org/archives/list/users@ovirt.org/thread/XI3LV4GPACT7IL… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2728) Old emails resurfacing
by Benny Zlotnik (oVirt JIRA) 15 May '19

15 May '19

Benny Zlotnik created OVIRT-2728: ------------------------------------ Summary: Old emails resurfacing Key: OVIRT-2728 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2728 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Benny Zlotnik Assignee: infra Hi, Public lists, especially users@ovirt, have a large amount of emails from 2016 resurfacing[1] This pushes down actual new and relevant emails from users, also some new emails don't reach my inbox[2] [1] - https://lists.ovirt.org/archives/list/users@ovirt.org/thread/BW5EV5PFIXRBT6… [2] - https://lists.ovirt.org/archives/list/users@ovirt.org/thread/XI3LV4GPACT7IL… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #558
by jenkins＠jenkins.phx.ovirt.org 15 May '19

15 May '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> ------------------------------------------ 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-fedora-updates-fc29-x86_64…> 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune 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:1816) 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': Failed connect to gerrit.ovirt.org:80; Connection timed out at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) 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.GeneratedMethodAccessor301.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.$Proxy94.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:1816) 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 1

oVirt infra daily report - unstable production jobs - 825
by jenkins＠jenkins.phx.ovirt.org 15 May '19

15 May '19

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/825//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99979,1 (cockpit-ovirt) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 May '19

14 May '19

Change 99979,1 (cockpit-ovirt) 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/99979/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/874/

2 1

[CQ]: 99736,5 (safelease) failed "ovirt-master" system tests
by oVirt Jenkins 14 May '19

14 May '19

Change 99736,5 (safelease) 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/99736/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14120/

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- Sudo isn't needed for the cleanup, you just need to login to the VM, which is done from the jump host, so no need for sudo. > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Barak Korren (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2725: ------------------------------------- We can't have sudo access on the s390x node - its not owned by us. > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Anton Marchukov (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2725: ---------------------------------------- Per [~eyonasi(a)redhat.com] there is a cleanup but it fails without sudo, so if we can arrange sudo access for Jenkins then it the cleanup should work. > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Anton Marchukov (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2725: ----------------------------------- Issue Type: Task (was: By-EMAIL) > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Anton Marchukov (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2725: ---------------------------------------- [~szidmi] can you check if this something you can help with? [~ederevea] FYI. > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[CQ]: 98774,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 May '19

14 May '19

Change 98774,3 (ovirt-engine) 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/98774/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14114/

3 3

[CQ]: 99967,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 May '19

14 May '19

Change 99967,1 (ovirt-engine) 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/99967/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/873/

2 1

Build failed in Jenkins: system-sync_mirrors-mock-copr-el7-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 14 May '19

14 May '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/1/dis…> ------------------------------------------ Started by user Barak Korren [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/ws/> No credentials specified Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <http://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-el7-x86_64/ws/je…> # 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse refs/changes/76/99976/1^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/changes/76/99976/1^{commit} # timeout=10 > git rev-parse refs/changes/76/99976/1^{commit} # timeout=10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

1 2

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 104 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 May '19

14 May '19

Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build Number: 104 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #104 [Sandro Bonazzola] centos: switch to 4.4 testing repos [Barak Korren] build_images: Run with STDCI [Barak Korren] update_images: Add playbook for image updating [Sandro Bonazzola] ovirt-engine: add fc29 on master [Barak Korren] mirror_client: Fix race condition in tests ----------------- Failed Tests: ----------------- No tests ran.

1 3

[JIRA] (OVIRT-2727) Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer
by Eyal Edri (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2727?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2727: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer > -------------------------------------------------------------------- > > Key: OVIRT-2727 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2727 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please grant Ales +2 access on ovirt-engine > ---------- Forwarded message --------- > From: Greg Sheremeta <gshereme(a)redhat.com> > Date: Mon, May 13, 2019 at 2:52 PM > Subject: Re: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer > To: devel <devel(a)ovirt.org>, Ales Musil <amusil(a)redhat.com> > Thanks everyone. Ales, congrats, and be careful :) > On Mon, May 13, 2019 at 12:11 PM Tal Nisan <tnisan(a)redhat.com> wrote: > > +1 > > > > On Thu, May 9, 2019 at 9:37 AM Tomas Jelinek <tjelinek(a)redhat.com> wrote: > > > >> > >> > >> On Sun, May 5, 2019 at 8:10 PM Daniel Erez <derez(a)redhat.com> wrote: > >> > >>> > >>> > >>> On Thu, May 2, 2019 at 9:42 PM Greg Sheremeta <gshereme(a)redhat.com> > >>> wrote: > >>> > >>>> Hi all, > >>>> > >>>> I'd like to propose Ales Musil as a frontend maintainer for network > >>>> parts of the admin portal UI. Since joining the team 2 years ago, Ales has > >>>> quickly become very knowledgeable about all of the GWT intricacies of the > >>>> admin portal. I trust his expertise and judgment. > >>>> > >>> > >> +1 fur sure! > >> > >> > >>> > >>> +1 > >>> > >>> > >>>> > >>>> Best wishes, > >>>> Greg > >>>> > >>>> -- > >>>> > >>>> Greg Sheremeta > >>>> > >>>> Senior Software Engineer > >>>> > >>>> Red Hat <https://www.redhat.com/> > >>>> <https://www.redhat.com/> > >>>> _______________________________________________ > >>>> Devel mailing list -- devel(a)ovirt.org > >>>> To unsubscribe send an email to devel-leave(a)ovirt.org > >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >>>> oVirt Code of Conduct: > >>>> https://www.ovirt.org/community/about/community-guidelines/ > >>>> List Archives: > >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ML5UVKYABG744… > >>>> > >>> _______________________________________________ > >>> Devel mailing list -- devel(a)ovirt.org > >>> To unsubscribe send an email to devel-leave(a)ovirt.org > >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >>> oVirt Code of Conduct: > >>> https://www.ovirt.org/community/about/community-guidelines/ > >>> List Archives: > >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/N7WW4AWIZQII5… > >>> > >> _______________________________________________ > >> Devel mailing list -- devel(a)ovirt.org > >> To unsubscribe send an email to devel-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QLLIXIVBQ2SKB… > >> > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OWAOTCLUMK7LN… > > > -- > Greg Sheremeta > Senior Software Engineer, Service Delivery > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> > -- > Greg Sheremeta > Senior Software Engineer, Service Delivery > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

[JIRA] (OVIRT-2727) Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer
by Eyal Edri (oVirt JIRA) 14 May '19

14 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2727?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2727: ---------------------------------- Added ales to 'ovirt-engine-master-maintainers'. BTW, I believe you don't need to wait for someone from infra to do it, and any of the existing maintainers can add an addition maintainer to the group AFAIK. > Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer > -------------------------------------------------------------------- > > Key: OVIRT-2727 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2727 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please grant Ales +2 access on ovirt-engine > ---------- Forwarded message --------- > From: Greg Sheremeta <gshereme(a)redhat.com> > Date: Mon, May 13, 2019 at 2:52 PM > Subject: Re: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer > To: devel <devel(a)ovirt.org>, Ales Musil <amusil(a)redhat.com> > Thanks everyone. Ales, congrats, and be careful :) > On Mon, May 13, 2019 at 12:11 PM Tal Nisan <tnisan(a)redhat.com> wrote: > > +1 > > > > On Thu, May 9, 2019 at 9:37 AM Tomas Jelinek <tjelinek(a)redhat.com> wrote: > > > >> > >> > >> On Sun, May 5, 2019 at 8:10 PM Daniel Erez <derez(a)redhat.com> wrote: > >> > >>> > >>> > >>> On Thu, May 2, 2019 at 9:42 PM Greg Sheremeta <gshereme(a)redhat.com> > >>> wrote: > >>> > >>>> Hi all, > >>>> > >>>> I'd like to propose Ales Musil as a frontend maintainer for network > >>>> parts of the admin portal UI. Since joining the team 2 years ago, Ales has > >>>> quickly become very knowledgeable about all of the GWT intricacies of the > >>>> admin portal. I trust his expertise and judgment. > >>>> > >>> > >> +1 fur sure! > >> > >> > >>> > >>> +1 > >>> > >>> > >>>> > >>>> Best wishes, > >>>> Greg > >>>> > >>>> -- > >>>> > >>>> Greg Sheremeta > >>>> > >>>> Senior Software Engineer > >>>> > >>>> Red Hat <https://www.redhat.com/> > >>>> <https://www.redhat.com/> > >>>> _______________________________________________ > >>>> Devel mailing list -- devel(a)ovirt.org > >>>> To unsubscribe send an email to devel-leave(a)ovirt.org > >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >>>> oVirt Code of Conduct: > >>>> https://www.ovirt.org/community/about/community-guidelines/ > >>>> List Archives: > >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ML5UVKYABG744… > >>>> > >>> _______________________________________________ > >>> Devel mailing list -- devel(a)ovirt.org > >>> To unsubscribe send an email to devel-leave(a)ovirt.org > >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >>> oVirt Code of Conduct: > >>> https://www.ovirt.org/community/about/community-guidelines/ > >>> List Archives: > >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/N7WW4AWIZQII5… > >>> > >> _______________________________________________ > >> Devel mailing list -- devel(a)ovirt.org > >> To unsubscribe send an email to devel-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QLLIXIVBQ2SKB… > >> > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OWAOTCLUMK7LN… > > > -- > Greg Sheremeta > Senior Software Engineer, Service Delivery > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> > -- > Greg Sheremeta > Senior Software Engineer, Service Delivery > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

1 0

oVirt infra daily report - unstable production jobs - 824
by jenkins＠jenkins.phx.ovirt.org 14 May '19

14 May '19

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/824//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 47f3db5 (v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 May '19

13 May '19

Change 47f3db5 (v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/v2v-conversion-host/commit/47f3db53883f2133b5ba5e7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4339/

1 0

[JIRA] (OVIRT-2727) Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer
by Greg Sheremeta (oVirt JIRA) 13 May '19

13 May '19

Greg Sheremeta created OVIRT-2727: ------------------------------------- Summary: Fwd: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer Key: OVIRT-2727 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2727 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Please grant Ales +2 access on ovirt-engine ---------- Forwarded message --------- From: Greg Sheremeta <gshereme(a)redhat.com> Date: Mon, May 13, 2019 at 2:52 PM Subject: Re: [ovirt-devel] Re: proposing Ales Musil as a frontend maintainer To: devel <devel(a)ovirt.org>, Ales Musil <amusil(a)redhat.com> Thanks everyone. Ales, congrats, and be careful :) On Mon, May 13, 2019 at 12:11 PM Tal Nisan <tnisan(a)redhat.com> wrote: > +1 > > On Thu, May 9, 2019 at 9:37 AM Tomas Jelinek <tjelinek(a)redhat.com> wrote: > >> >> >> On Sun, May 5, 2019 at 8:10 PM Daniel Erez <derez(a)redhat.com> wrote: >> >>> >>> >>> On Thu, May 2, 2019 at 9:42 PM Greg Sheremeta <gshereme(a)redhat.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I'd like to propose Ales Musil as a frontend maintainer for network >>>> parts of the admin portal UI. Since joining the team 2 years ago, Ales has >>>> quickly become very knowledgeable about all of the GWT intricacies of the >>>> admin portal. I trust his expertise and judgment. >>>> >>> >> +1 fur sure! >> >> >>> >>> +1 >>> >>> >>>> >>>> Best wishes, >>>> Greg >>>> >>>> -- >>>> >>>> Greg Sheremeta >>>> >>>> Senior Software Engineer >>>> >>>> Red Hat <https://www.redhat.com/> >>>> <https://www.redhat.com/> >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ML5UVKYABG744… >>>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/N7WW4AWIZQII5… >>> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QLLIXIVBQ2SKB… >> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OWAOTCLUMK7LN… > -- Greg Sheremeta Senior Software Engineer, Service Delivery Red Hat <https://www.redhat.com/> <https://www.redhat.com/> -- Greg Sheremeta Senior Software Engineer, Service Delivery Red Hat <https://www.redhat.com/> <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on lfedora1.lf-dev.marist.edu.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0091.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0089.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0044.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0038.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0003.workers-phx.ovirt.org.

1 0