- Infra - oVirt List Archives

[CQ]: 99800,2 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 99800,2 (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/99800/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/999/

1 0

[CQ]: 100335,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 May '19

28 May '19

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

1 0

[CQ]: 100079, 1 (ovirt-engine-api-explorer) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 100079,1 (ovirt-engine-api-explorer) 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://gerrit.ovirt.org/#/c/100079/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4426/

1 0

[CQ]: 99824, 7 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '19

28 May '19

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

1 0

[JIRA] (OVIRT-2734) Fwd: [ovirt-infra] one of s390x agents ran out of disk space
by Ehud Yonasi (oVirt JIRA) 28 May '19

28 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2734?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2734: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Fwd: [ovirt-infra] one of s390x agents ran out of disk space > ------------------------------------------------------------ > > Key: OVIRT-2734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2734 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Ehud Yonasi > > Forwarding to infra-support to create a ticket. > > Begin forwarded message: > > > > From: Marcin Sobczyk <msobczyk(a)redhat.com> > > Subject: [ovirt-infra] one of s390x agents ran out of disk space > > Date: 28 May 2019 at 11:23:20 CEST > > To: infra <infra(a)ovirt.org> > > > > Hi, > > > > it seems that one of our s390x agents ran out of disk space, piece of log from my CI job: > > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] cp: cannot create directory '/tmp/tmp.mock_runner.jLl/ci_toolbox': No space left on device > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 373: echo: write error: No space left on device > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 374: echo: write error: No space left on device > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 375: echo: write error: No space left on device > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 376: echo: write error: No space left on device > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:06.089Z] sh: line 0: echo: write error: No space left on device > > Link to failing job: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…> > > Regards, Marcin > > > > > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-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/infra@ovirt.org/message/FTMRUC5OXBDRR… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[oVirt CI] standard-enqueue - Build #21456 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 May '19

28 May '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/21456/ Build Name: #21456 Build Description: Gerrit: 99777 - cockpit-ovirt (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/99777 - title: Introduce Vagrant Local Development Environment - project: cockpit-ovirt - branch: master - author: Evgeny Slutsky <>

1 0

[JIRA] (OVIRT-2734) Fwd: [ovirt-infra] one of s390x agents ran out of disk space
by Anton Marchukov (oVirt JIRA) 28 May '19

28 May '19

Anton Marchukov created OVIRT-2734: -------------------------------------- Summary: Fwd: [ovirt-infra] one of s390x agents ran out of disk space Key: OVIRT-2734 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2734 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Forwarding to infra-support to create a ticket. > Begin forwarded message: > > From: Marcin Sobczyk <msobczyk(a)redhat.com> > Subject: [ovirt-infra] one of s390x agents ran out of disk space > Date: 28 May 2019 at 11:23:20 CEST > To: infra <infra(a)ovirt.org> > > Hi, > > it seems that one of our s390x agents ran out of disk space, piece of log from my CI job: > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] cp: cannot create directory '/tmp/tmp.mock_runner.jLl/ci_toolbox': No space left on device > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 373: echo: write error: No space left on device > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 374: echo: write error: No space left on device > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 375: echo: write error: No space left on device > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 376: echo: write error: No space left on device > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:06.089Z] sh: line 0: echo: write error: No space left on device > Link to failing job: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…> > Regards, Marcin > > > > > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-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/infra@ovirt.org/message/FTMRUC5OXBDRR… -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

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

28 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2730: -------------------------------------- Assignee: Barak Korren (was: infra) > 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: Barak Korren > > 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#100103)

1 0

[JIRA] (OVIRT-2731) Can't docker push when using newer docker daemon?
by Anton Marchukov (oVirt JIRA) 28 May '19

28 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2731?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2731: -------------------------------------- Assignee: Ehud Yonasi (was: infra) > Can't docker push when using newer docker daemon? > ------------------------------------------------- > > Key: OVIRT-2731 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2731 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: Ehud Yonasi > > With this patch > <https://github.com/oVirt/ovirt-openshift-extensions/pull/136>I'm building > multi-stage images in my builds, and I'm trying to push them to quay. > The docker push was working without any problems before the daemon change. > The difference is that now the docker client is inside a container, which > is inside mock, which has > the docker socket of a docker daemon version 18. > Docker login succeeds according to the job logs > The push when uploading layers: > [2019-05-19T06:12:03.008Z] + make push-containers PUSH_LATEST=0 > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > Login Succeeded > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > docker push quay.io/rgolangh/ovirt-flexvolume-driver:0.4.0-11.gd0ead0b > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > The push refers to repository > [quay.io/rgolangh/ovirt-flexvolume-driver] > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > bf535c6e5461: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > e6318b33302c: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > a3890b39a2b2: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > e78e5b504103: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > f7fa4accb0ea: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > 35265ad107f5: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > 4765a2d3f85d: Preparing > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > 35265ad107f5: Waiting > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > 4765a2d3f85d: Waiting > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > unauthorized: access to the requested resource is not authorized > <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshift-…>[2019-05-19T06:12:03.008Z] > make: *** [container-push-ovirt-flexvolume-driver] Error 1 > Can I get the daemon logs? anyone see it? any advice? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[ovirt-infra] one of s390x agents ran out of disk space
by Marcin Sobczyk 28 May '19

28 May '19

Hi, it seems that one of our s390x agents ran out of disk space, piece of log from my CI job: <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] cp: cannot create directory '/tmp/tmp.mock_runner.jLl/ci_toolbox': No space left on device <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 373: echo: write error: No space left on device <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 374: echo: write error: No space left on device <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 375: echo: write error: No space left on device <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:03.944Z] ../jenkins/mock_configs/mock_runner.sh: line 376: echo: write error: No space left on device <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-05-28T09:07:06.089Z] sh: line 0: echo: write error: No space left on device Link to failing job: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… Regards, Marcin

1 0

[CQ]: 100324,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 28 May '19

28 May '19

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

1 0

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

28 May '19

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

1 1

[CQ]: 100321, 2 (ovirt-host-deploy) failed "ovirt-master" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 100321,2 (ovirt-host-deploy) 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/100321/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14280/

1 0

[CQ]: 99950,21 (mom) failed "ovirt-master" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 99950,21 (mom) 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/99950/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14278/

1 0

[CQ]: 99950,21 (mom) failed "ovirt-master" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 99950,21 (mom) 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/99950/21 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14275/

1 0

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

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

1 0

[CQ]: 100289,2 (mom) failed "ovirt-master" system tests
by oVirt Jenkins 27 May '19

27 May '19

Change 100289,2 (mom) 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/100289/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14269/

1 0

Build failed in Jenkins: deploy-to_ovirt-master_tested #7684
by jenkins＠jenkins.phx.ovirt.org 27 May '19

27 May '19

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/7684/display/red…> ------------------------------------------ [...truncated 1.43 KB...] [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/workspace/deploy-to_ovirt-master_tested(a)tmp/private_key_8528729764101711110.key (/home/jenkins/workspace/deploy-to_ovirt-master_tested(a)tmp/private_key_8528729764101711110.key) [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-master_tested] $ /bin/bash -xe /tmp/jenkins7738032543608199772.sh + [[ http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… == '' ]] + queue_name=ovirt-master + echo repo-extra-dir:master + echo http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org Pseudo-terminal will not be allocated because stdin is not a terminal. + BASE_DIR=/srv/resources/repos/ovirt/tested + PUBLISH_MD_COPIES=50 + main + local tmp_dir + mkdir -p /srv/resources/repos/ovirt/tested ++ mktemp -d /srv/resources/repos/ovirt/tested/.deploy.XXXXXXXXXX Collecting packages + tmp_dir=/srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 + trap 'rm -rf '\''/srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59'\''' EXIT HUP + echo 'Collecting packages' + collect_packages /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 + local repoman_dst=/srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 + repoman --temp-dir generate-in-repo --option main.allowed_repo_paths=/srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 --option main.on_empty_source=warn /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 add conf:stdin 2019-05-27 15:33:03,271::INFO::repoman.cmd:: 2019-05-27 15:33:03,271::INFO::repoman.cmd::Adding artifacts to the repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 2019-05-27 15:33:03,271::INFO::repoman.common.repo::Adding repo extra dir master 2019-05-27 15:33:03,273::INFO::repoman.common.stores.RPM::Loading repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:33:03,273::INFO::repoman.common.stores.RPM::Repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master loaded 2019-05-27 15:33:03,274::INFO::repoman.common.stores.iso::Loading repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:33:03,275::INFO::repoman.common.stores.iso::Repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master loaded 2019-05-27 15:33:03,283::INFO::repoman.common.repo::Resolving artifact source http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… 2019-05-27 15:33:03,460::INFO::repoman.common.sources.jenkins::Parsing jenkins URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… 2019-05-27 15:33:03,461::INFO::repoman.common.sources.jenkins:: Got URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… 2019-05-27 15:33:03,461::INFO::repoman.common.sources.jenkins:: Got URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… 2019-05-27 15:33:03,462::INFO::root:: Done 2019-05-27 15:33:03,792::INFO::root::Downloading http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86…, length 906M ... %[-----------------------25------------------------50-----------------------75------------------------] %[====================================================================================================] 2019-05-27 15:33:24,004::INFO::repoman.common.stores.RPM::Adding package /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/.lago_tmp/tmprLwHS_/tmpgqB5Fn/ovirt-engine-appliance-4.4-20190527.1.el7.src.rpm to repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:33:24,096::INFO::root::Downloading http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86…, length 906M ... %[-----------------------25------------------------50-----------------------75------------------------] %[====================================================================================================] 2019-05-27 15:33:45,259::INFO::repoman.common.stores.RPM::Adding package /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/.lago_tmp/tmprLwHS_/tmpgqB5Fn/ovirt-engine-appliance-4.4-20190527.1.el7.x86_64.rpm to repo /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:33:45,260::INFO::repoman.cmd:: 2019-05-27 15:33:45,260::INFO::repoman.common.stores.RPM::Saving new added rpms into /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:33:45,261::INFO::root::Saving /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master/rpm/el7/SRPMS/ovirt-engine-appliance-4.4-20190527.1.el7.src.rpm 2019-05-27 15:33:45,264::INFO::root::Saving /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master/rpm/el7/x86_64/ovirt-engine-appliance-4.4-20190527.1.el7.x86_64.rpm 2019-05-27 15:33:45,266::INFO::repoman.common.stores.RPM:: 2019-05-27 15:33:45,266::INFO::repoman.common.stores.RPM::Updating metadata 2019-05-27 15:33:45,266::INFO::repoman.common.stores.RPM:: Creating metadata for el7 2019-05-27 15:34:11,412::INFO::repoman.common.stores.RPM:: 2019-05-27 15:34:11,412::INFO::repoman.common.stores.RPM::Creating symlinks 2019-05-27 15:34:11,413::INFO::repoman.common.stores.RPM:: 2019-05-27 15:34:11,413::INFO::repoman.common.stores.RPM::Saved /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:34:11,413::INFO::repoman.common.stores.iso::Saving new added isos into /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:34:11,413::INFO::repoman.common.stores.iso:: 2019-05-27 15:34:11,413::INFO::repoman.common.stores.iso::Saved /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/master 2019-05-27 15:34:11,415::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/.lago_tmp/tmprLwHS_/tmpgqB5Fn 2019-05-27 15:34:11,415::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59/.lago_tmp/tmprLwHS_ Publishing to repo + echo 'Publishing to repo' + push_to_tested /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 /srv/resources/repos/ovirt/tested + local pkg_src=/srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 + local pkg_dst=/srv/resources/repos/ovirt/tested + cd /srv/resources/repos/ovirt/tested/.deploy.TXuRNv8j59 + tac + read dir + find . -type d '!' -name repodata + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/./.lago_tmp + find ./.lago_tmp -maxdepth 1 '!' -type d -print0 + xargs -0 -r cp -RPplf -t /srv/resources/repos/ovirt/tested/./.lago_tmp + [[ -d ./.lago_tmp/repodata ]] + read dir + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/./master/rpm/el7/x86_64 + find ./master/rpm/el7/x86_64 -maxdepth 1 '!' -type d -print0 + xargs -0 -r cp -RPplf -t /srv/resources/repos/ovirt/tested/./master/rpm/el7/x86_64 + [[ -d ./master/rpm/el7/x86_64/repodata ]] + read dir + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/./master/rpm/el7/SRPMS + find ./master/rpm/el7/SRPMS -maxdepth 1 '!' -type d -print0 + xargs -0 -r cp -RPplf -t /srv/resources/repos/ovirt/tested/./master/rpm/el7/SRPMS + [[ -d ./master/rpm/el7/SRPMS/repodata ]] + xargs -L 1 -P 8 -r rm -f + comm -23 /dev/fd/63 /dev/fd/62 ++ repomanage -k1 --new -c /srv/resources/repos/ovirt/tested/./master/rpm/el7/SRPMS ++ sort ++ find /srv/resources/repos/ovirt/tested/master/rpm/el7/SRPMS -name '*.rpm' -type f -mtime +14 ++ sort + createrepo_c --update --retain-old-md 50 --workers 8 /srv/resources/repos/ovirt/tested/./master/rpm/el7/SRPMS Directory walk started Directory walk done - 219 packages Loaded information about 218 packages Temporary output repo path: /srv/resources/repos/ovirt/tested/./master/rpm/el7/SRPMS/.repodata/ Preparing sqlite DBs Pool started (with 8 workers) Pool finished + read dir + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/./master/rpm/el7 + find ./master/rpm/el7 -maxdepth 1 '!' -type d -print0 + xargs -0 -r cp -RPplf -t /srv/resources/repos/ovirt/tested/./master/rpm/el7 + [[ -d ./master/rpm/el7/repodata ]] + xargs -L 1 -P 8 -r rm -f + comm -23 /dev/fd/63 /dev/fd/62 ++ repomanage -k1 --new -c /srv/resources/repos/ovirt/tested/./master/rpm/el7 ++ find /srv/resources/repos/ovirt/tested/master/rpm/el7 -name '*.rpm' -type f -mtime +14 ++ sort ++ sort + createrepo_c --update --retain-old-md 50 --workers 8 /srv/resources/repos/ovirt/tested/./master/rpm/el7 FATAL: command execution failed java.io.IOException at hudson.remoting.Channel.close(Channel.java:1449) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:832) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:799) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at jenkins.model.Jenkins.access$2200(Jenkins.java:309) at jenkins.model.Jenkins$19.run(Jenkins.java:3432) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3426) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3301) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:960) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:571) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:937) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:381) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1004) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:297) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:149) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:170) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:462) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:310) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on vm0164.workers-phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:950) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy89.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1144) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1136) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 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) FATAL: Unable to delete script file /tmp/jenkins7738032543608199772.sh java.io.IOException at hudson.remoting.Channel.close(Channel.java:1449) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:832) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:799) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at jenkins.model.Jenkins.access$2200(Jenkins.java:309) at jenkins.model.Jenkins$19.run(Jenkins.java:3432) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3426) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3301) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:960) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:571) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:937) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:381) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1004) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:297) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:149) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:170) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:462) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:310) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on vm0164.workers-phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:950) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.FilePath.delete(FilePath.java:1539) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 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) Build step 'Execute shell' marked build as failure FATAL: Channel "unknown": Remote call on vm0164.workers-phx.ovirt.org failed. The channel is closing down or has closed down java.io.IOException at hudson.remoting.Channel.close(Channel.java:1449) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:832) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:799) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at jenkins.model.Jenkins.access$2200(Jenkins.java:309) at jenkins.model.Jenkins$19.run(Jenkins.java:3432) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3426) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3301) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:960) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:571) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:937) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:381) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1004) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:297) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:149) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:170) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:462) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:310) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on vm0164.workers-phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:950) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1059) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.stop(ExecRemoteAgent.java:130) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.tearDown(SSHAgentBuildWrapper.java:417) at hudson.model.Build$BuildExecution.doRun(Build.java:174) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 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)

1 2

[CQ]: 100237,4 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 May '19

27 May '19

Change 100237,4 (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/100237/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/982/

1 0

Re: [ovirt-users] Donating hardware to the oVirt project - a great opportunity to contribute
by Eyal Edri 27 May '19

27 May '19

Also adding infra and devel lists. On Thu, May 23, 2019 at 11:19 AM Evgheni Dereveanchin <ederevea(a)redhat.com> wrote: > Hi everyone, > > My name is Evgheni and I'm in charge of the infrastructure used by oVirt > to host the code, test it and serve packages to users. Currently we heavily > rely on our PHX data center [1] for these tasks. It consists of several > dozen bare metal servers that work as hypervisors, storage servers and bare > metal CI hosts. We use them quite effectively yet the amount of workload is > always growing so now is a good time to ask our community for help. If you > happen to have physical servers or VMs that could be used as part of oVirt > infra - please let us know. We created a page [2] describing hardware specs > that would allow us make the infra more stable and grow its capacity. > > If you have any other ideas or input about the oVirt infra - feel free to > reach out to me or start a discussion on the Infra list [3]. > > Regards, > Evgheni > > [1] > https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Overview/inde… > [2] https://ovirt.org/community/get-involved/donate-hardware.html > [3] https://lists.ovirt.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/H3BHMU3DHFS7N… > -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)

1 0

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

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3694 kubevirt [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 openshift-kubevirt-org-84f4z.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3691 kubevirt [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 openshift-kubevirt-org-3rkgr.

1 7

[JIRA] (OVIRT-2733) Maintainers of ovirt-engine-cli project in gerrit.ovirt.org
by Eyal Edri (oVirt JIRA) 26 May '19

26 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2733?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2733: ----------------------------- Resolution: Fixed Status: Done (was: To Do) added > Maintainers of ovirt-engine-cli project in gerrit.ovirt.org > ----------------------------------------------------------- > > Key: OVIRT-2733 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2733 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: infra > Priority: High > > Hi, > could you please add [~omachace(a)redhat.com] and [~oliel(a)redhat.com] to ovirt-engine-cli-maintainers group so they will have full maintainers permissions for ovirt-engine-cli project? > Thanks > M. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2337) Ensure emergency access to PHX production VMs
by Eyal Edri (oVirt JIRA) 26 May '19

26 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2337?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2337: ---------------------------------- [~ederevea] can [~szidmi] help with this task? > Ensure emergency access to PHX production VMs > --------------------------------------------- > > Key: OVIRT-2337 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2337 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure that in case of malfunction we have multiple fail-safe ways of gaining access to the PHX production VMs to resolve issues. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #1478 containerized-data-importer [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 openshift-kubevirt-org-9t3rf.

1 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3691 kubevirt [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 openshift-kubevirt-org-xkbgw.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3691 kubevirt [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 openshift-kubevirt-org-ck31x.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3691 kubevirt [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 openshift-kubevirt-org-8qg6k.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3690 kubevirt [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 openshift-kubevirt-org-jvn39.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3690 kubevirt [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 openshift-kubevirt-org-r18j0.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3690 kubevirt [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 openshift-kubevirt-org-2cx9l.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3690 kubevirt [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 openshift-kubevirt-org-97gzt.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3690 kubevirt [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 openshift-kubevirt-org-fxmcn.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-87zhf.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-0p8qq.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-62m9q.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-29rpf.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-w0wd4.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-z758l.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3689 kubevirt [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 openshift-kubevirt-org-84ks9.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3688 kubevirt [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 openshift-kubevirt-org-3883g.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3688 kubevirt [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 openshift-kubevirt-org-2w3nx.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3688 kubevirt [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 openshift-kubevirt-org-4w9zb.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 May '19

26 May '19

Failed to run project_setup.sh for: #3688 kubevirt [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 openshift-kubevirt-org-m4xcs.

1 0

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

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

1 0

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

25 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/588/ Build Number: 588 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #588 [Galit Rosenthal] Add retrie to wait for hosts to be up [Sandro Bonazzola] ovirt-engine-api-explorer: add fc29 jobs ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 006_migrations.migrate_vm_42 Error Message: Failed to call vdsm-client in lago-compat-4-2-suite-master-host-1, vdsm-client: Command Host.getVMList with args {} failed: (code=-32603, message=Internal JSON-RPC error: {'reason': 'status() takes exactly 1 argument (2 given)'}) -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-2-suite-master-host-1 destination host: lago-compat-4-2-suite-master-host-0 --------------------- >> end captured stdout << ---------------------- -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:86f92043-3541-4638-8cbd-73c9209b59bf:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: end task:86f92043-3541-4638-8cbd-73c9209b59bf:Get ssh client for lago-compat-4-2-suite-master-host-1: lago.ssh: DEBUG: Running 374461be on lago-compat-4-2-suite-master-host-1: vdsm-client Host getVMList lago.ssh: DEBUG: Command 374461be on lago-compat-4-2-suite-master-host-1 returned with 1 lago.ssh: DEBUG: Command 374461be on lago-compat-4-2-suite-master-host-1 errors: vdsm-client: Command Host.getVMList with args {} failed: (code=-32603, message=Internal JSON-RPC error: {'reason': 'status() takes exactly 1 argument (2 given)'}) ovirtlago.testlib: ERROR: * Unhandled exception in <function vm_is_not_on_host at 0x7fcf6858a410> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/006_migrations.py", line 103, in vm_is_not_on_host src_host, ret.err RuntimeError: Failed to call vdsm-client in lago-compat-4-2-suite-master-host-1, vdsm-client: Command Host.getVMList with args {} failed: (code=-32603, message=Internal JSON-RPC error: {'reason': 'status() takes exactly 1 argument (2 given)'}) --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/006_migrations.py", line 111, in migrate_vm testlib.assert_true_within_short(vm_is_not_on_host) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/006_migrations.py", line 103, in vm_is_not_on_host src_host, ret.err 'Failed to call vdsm-client in lago-compat-4-2-suite-master-host-1, vdsm-client: Command Host.getVMList with args {} failed:\n(code=-32603, message=Internal JSON-RPC error: {\'reason\': \'status() takes exactly 1 argument (2 given)\'})\n\n-------------------- >> begin captured stdout << ---------------------\nsource host: lago-compat-4-2-suite-master-host-1\ndestination host: lago-compat-4-2-suite-master-host-0\n\n--------------------- >> end captured stdout << ----------------------\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:86f92043-3541-4638-8cbd-73c9209b59bf:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: end task:86f92043-3541-4638-8cbd-73c9209b59bf:Get ssh client for lago-compat-4-2-suite-master-host-1:\nlago.ssh: DEBUG: Running 374461be on lago-compat-4-2-suite-master-host-1: vdsm-client Host getVMList\nlago.ssh: DEBUG: Command 374461be on lago-compat-4-2-suite-master-host-1 returned with 1\nlago.ssh: DEBUG: Command 374461be on lago-compat-4-2-suite-master-host-1 errors:\n vdsm-client: Command Host.getVMList with args {} failed:\n(code=-32603, message=Internal JSON-RPC error: {\'reason\': \'status() takes exactly 1 argument (2 given)\'})\n\novirtlago.testlib: ERROR: * Unhandled exception in <function vm_is_not_on_host at 0x7fcf6858a410>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/006_migrations.py", line 103, in vm_is_not_on_host\n src_host, ret.err\nRuntimeError: Failed to call vdsm-client in lago-compat-4-2-suite-master-host-1, vdsm-client: Command Host.getVMList with args {} failed:\n(code=-32603, message=Internal JSON-RPC error: {\'reason\': \'status() takes exactly 1 argument (2 given)\'})\n\n--------------------- >> end captured logging << ---------------------'

1 1

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

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

1 0

[JIRA] (OVIRT-2733) Maintainers of ovirt-engine-cli project in gerrit.ovirt.org
by Martin Perina (oVirt JIRA) 24 May '19

24 May '19

Martin Perina created OVIRT-2733: ------------------------------------ Summary: Maintainers of ovirt-engine-cli project in gerrit.ovirt.org Key: OVIRT-2733 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2733 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Martin Perina Assignee: infra Priority: High Hi, could you please add [~omachace(a)redhat.com] and [~oliel(a)redhat.com] to ovirt-engine-cli-maintainers group so they will have full maintainers permissions for ovirt-engine-cli project? Thanks M. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

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

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

1 0