May 2019 - Infra - oVirt List Archives

[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