- Infra - oVirt List Archives

[JIRA] (OVIRT-2659) Urgent: ChangeQueue is broken
by Eyal Edri (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2659?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2659: ----------------------------- Assignee: Daniel Belenky (was: infra) Resolution: Fixed Status: Done (was: To Do) this was solved, caused by a missing pkg on the loader node. [~dbelenky(a)redhat.com] solved it and can add more info > Urgent: ChangeQueue is broken > ----------------------------- > > Key: OVIRT-2659 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2659 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: sbonazzo > Assignee: Daniel Belenky > > Jobs are not being added to change queue due to a bug: > https://jenkins.ovirt.org/job/standard-enqueue/18870/ > *00:03:06.321* Will enqueue to: ovirt-master[Pipeline] parallel > <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > { (Branch: ovirt-master) > <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > withEnv <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > { <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > sh (hide <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>)*00:03:07.538* > Traceback (most recent call last):*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue(a)tmp/durable-e69f565e/script.sh", > line 2, in <module>*00:03:07.539* from scripts.change_queue import > JenkinsChangeQueueClient*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/__init__.py", > line 14, in <module>*00:03:07.539* from .changes import > DisplayableChangeWrapper, ChangeInStreamWrapper, \*00:03:07.539* > File "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/changes/__init__.py", > line 15, in <module>*00:03:07.539* from scripts.gerrit import > GerritPatchset*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/gerrit.py", > line 10, in <module>*00:03:07.539* from paramiko.client import > SSHClient > *00:03:07.539* ImportError: No module named paramiko.client > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2659) Urgent: ChangeQueue is broken
by Eyal Edri (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2659?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2659: ----------------------------- Issue Type: Outage (was: By-EMAIL) > Urgent: ChangeQueue is broken > ----------------------------- > > Key: OVIRT-2659 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2659 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: sbonazzo > Assignee: infra > > Jobs are not being added to change queue due to a bug: > https://jenkins.ovirt.org/job/standard-enqueue/18870/ > *00:03:06.321* Will enqueue to: ovirt-master[Pipeline] parallel > <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > { (Branch: ovirt-master) > <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > withEnv <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > { <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] > sh (hide <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>)*00:03:07.538* > Traceback (most recent call last):*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue(a)tmp/durable-e69f565e/script.sh", > line 2, in <module>*00:03:07.539* from scripts.change_queue import > JenkinsChangeQueueClient*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/__init__.py", > line 14, in <module>*00:03:07.539* from .changes import > DisplayableChangeWrapper, ChangeInStreamWrapper, \*00:03:07.539* > File "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/changes/__init__.py", > line 15, in <module>*00:03:07.539* from scripts.gerrit import > GerritPatchset*00:03:07.539* File > "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/gerrit.py", > line 10, in <module>*00:03:07.539* from paramiko.client import > SSHClient > *00:03:07.539* ImportError: No module named paramiko.client > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Greg Sheremeta reopened OVIRT-2662: ----------------------------------- > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2662: --------------------------------------- We've already done this several times. Next time he opens a PR, it will likely happen again. For example: https://github.com/oVirt/ovirt-web-ui/pull/904 why didn't that work? Why did he get it again on PR 931? > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 96178,9 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 24 Jan '19

24 Jan '19

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

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2662: ----------------------------- Resolution: Fixed Status: Done (was: To Do) solving it is just what the bot says to do :) a maintainer needs to write "ci add to whitelist" in order to allow the PR to run CI. I've just done it to the PR and it started running in CI > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Greg Sheremeta updated OVIRT-2662: ---------------------------------- Description: Please see https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 "As a security measure, I will not run automated tests on PRs that are not from white-listed contributors." The bot is lying -- I have 'add to whitelist' for Bohdan several times now. How do we cure this? -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> was: Please see https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 "As a security measure, I will not run automated tests on PRs that are not from white-listed contributors." The bot is lying -- it ran the tests, and I have 'add to whitelist' for Bohdan several times now. How do we cure this? -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2625) lists.ovirt.org not showing threads
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2625?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2625: --------------------------------------- still happening example: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/VUDGH7NUHOC35J… > lists.ovirt.org not showing threads > ----------------------------------- > > Key: OVIRT-2625 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2625 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_258.png > > > Hi, > lists.ovirt.org hyperkitty is once again not showing threads. I tried to > find my old Jira ticket, but Jira is down. > For example, this doesn't show the thread, but there are 8 replies: > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SDDH2OC5RBOVYY… > Screenshot: https://imgur.com/a/xHKDN6K > [image: Selection_258.png] > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

Greg Sheremeta created OVIRT-2662: ------------------------------------- Summary: jenkins whitelist issue in ovirt-web-ui Key: OVIRT-2662 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Please see https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 "As a security measure, I will not run automated tests on PRs that are not from white-listed contributors." The bot is lying -- it ran the tests, and I have 'add to whitelist' for Bohdan several times now. How do we cure this? -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2625) lists.ovirt.org not showing threads
by Greg Sheremeta (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2625?page=com.atlassian.jira.… ] Greg Sheremeta reopened OVIRT-2625: ----------------------------------- > lists.ovirt.org not showing threads > ----------------------------------- > > Key: OVIRT-2625 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2625 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_258.png > > > Hi, > lists.ovirt.org hyperkitty is once again not showing threads. I tried to > find my old Jira ticket, but Jira is down. > For example, this doesn't show the thread, but there are 8 replies: > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SDDH2OC5RBOVYY… > Screenshot: https://imgur.com/a/xHKDN6K > [image: Selection_258.png] > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

24 Jan '19

Failed to run project_setup.sh for: #3309 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-wh4fj.

1 0

[CQ]: 903aadb (ovirt-ansible-v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 24 Jan '19

24 Jan '19

Change 903aadb (ovirt-ansible-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/ovirt-ansible-v2v-conversion-host/commit/903aadbf2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3777/

1 0

[CQ]: 97220, 3 (ovirt-guest-agent) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jan '19

24 Jan '19

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

2 1

[JIRA] (OVIRT-2661) No space left on vm0038.workers-phx.ovirt.org
by sbonazzo (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2661: --------------------------------- Found it as no space left at job start: https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… > No space left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No space left on vm0038.workers-phx.ovirt.org
by sbonazzo (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2661: ---------------------------- Summary: No space left on vm0038.workers-phx.ovirt.org (was: No psace left on vm0038.workers-phx.ovirt.org) > No space left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No psace left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2661: -------------------------------- Issue Type: Outage (was: By-EMAIL) > No psace left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No psace left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2661: -------------------------------- Component/s: Jenkins Slaves > No psace left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No psace left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2661 at 1/24/19 12:38 PM: --------------------------------------------------------------- Where is the job that failed on that? The {{slave-cleanup}} script should have cleared enough space automatically was (Author: bkorren(a)redhat.com) Where is the job that failed on that? The `slave-cleanup` script should have cleared enough space automatically > No psace left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No psace left on vm0038.workers-phx.ovirt.org
by Barak Korren (oVirt JIRA) 24 Jan '19

24 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2661?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2661: ------------------------------------- Where is the job that failed on that? The `slave-cleanup` script should have cleared enough space automatically > No psace left on vm0038.workers-phx.ovirt.org > --------------------------------------------- > > Key: OVIRT-2661 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, took > https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ > offline due to no space left. > Can you please reprovision the VM and possibly add some more disk to it > while doing? > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2661) No psace left on vm0038.workers-phx.ovirt.org
by sbonazzo (oVirt JIRA) 24 Jan '19

24 Jan '19

sbonazzo created OVIRT-2661: ------------------------------- Summary: No psace left on vm0038.workers-phx.ovirt.org Key: OVIRT-2661 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2661 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, took https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org/ offline due to no space left. Can you please reprovision the VM and possibly add some more disk to it while doing? Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2660) Please cleanup oVirt Image Glance Repository
by sbonazzo (oVirt JIRA) 24 Jan '19

24 Jan '19

sbonazzo created OVIRT-2660: ------------------------------- Summary: Please cleanup oVirt Image Glance Repository Key: OVIRT-2660 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2660 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra oVirt Image Glance repository keeps lot of disks from distributions which reached end of life or have been obsoleted by new releases (CentOS, Fedora, Ubuntu and CirrOS). Can you please drop unsupported distributions images from the repository? -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[oVirt CI] standard-enqueue - Build #18868 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jan '19

24 Jan '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/18868/ Build Name: #18868 Build Description: Gerrit: 97227 - ovirt-provider-ovn (4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/97227 - title: build: ovirt-provider-ovn-1.2.19-1 - project: ovirt-provider-ovn - branch: master - author: Miguel Duarte Barroso <mdbarroso(a)redhat.com>

1 4

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #222
by jenkins＠jenkins.phx.ovirt.org 24 Jan '19

24 Jan '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…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 7d6c5113f814af2234e0d05d1e01f52ffa7258c2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 7d6c5113f814af2234e0d05d1e01f52ffa7258c2 Commit message: "Containerized loader node" > git rev-list --no-walk 7d6c5113f814af2234e0d05d1e01f52ffa7258c2 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins2542019165601063126.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2659) Urgent: ChangeQueue is broken
by sbonazzo (oVirt JIRA) 24 Jan '19

24 Jan '19

sbonazzo created OVIRT-2659: ------------------------------- Summary: Urgent: ChangeQueue is broken Key: OVIRT-2659 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2659 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Jobs are not being added to change queue due to a bug: https://jenkins.ovirt.org/job/standard-enqueue/18870/ *00:03:06.321* Will enqueue to: ovirt-master[Pipeline] parallel <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] { (Branch: ovirt-master) <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] withEnv <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] { <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>[Pipeline] sh (hide <https://jenkins.ovirt.org/job/standard-enqueue/18870/console#>)*00:03:07.538* Traceback (most recent call last):*00:03:07.539* File "/home/jenkins/workspace/standard-enqueue(a)tmp/durable-e69f565e/script.sh", line 2, in <module>*00:03:07.539* from scripts.change_queue import JenkinsChangeQueueClient*00:03:07.539* File "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/__init__.py", line 14, in <module>*00:03:07.539* from .changes import DisplayableChangeWrapper, ChangeInStreamWrapper, \*00:03:07.539* File "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/change_queue/changes/__init__.py", line 15, in <module>*00:03:07.539* from scripts.gerrit import GerritPatchset*00:03:07.539* File "/home/jenkins/workspace/standard-enqueue/jenkins/scripts/gerrit.py", line 10, in <module>*00:03:07.539* from paramiko.client import SSHClient *00:03:07.539* ImportError: No module named paramiko.client -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

24 Jan '19

Failed to run project_setup.sh for: #3298 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-nqwhb.

1 2

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

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

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3295 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-ph35p.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3295 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-5btxl.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #1139 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-z94hk.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3294 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-rmwhs.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3294 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-51gf6.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3294 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-4h5fw.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3293 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-fb9hm.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3293 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-l29ck.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3291 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-qhq2s.

1 2

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

23 Jan '19

Failed to run project_setup.sh for: #1138 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-flf8v.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3290 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-7fbmf.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #1137 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-4d43n.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #1137 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-bv1dd.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3287 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-dc09l.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3287 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-xf0w5.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3287 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-m9qjt.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3286 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-rsgmx.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3285 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-c7jll.

1 0

[oVirt CI] standard-enqueue - Build #18863 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/18863/ Build Name: #18863 Build Description: Gerrit: 96170 - ovirt-provider-ovn (4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/96170 - title: integration-tests: add a role to configure the ovn data plane - project: ovirt-provider-ovn - branch: master - author: Miguel Duarte Barroso <mdbarroso(a)redhat.com>

1 0

[oVirt CI] standard-enqueue - Build #18861 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/18861/ Build Name: #18861 Build Description: Gerrit: 97262 - ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/97262 - title: storage: Make default domain verion V4 for 4.3 - project: ovirt-engine - branch: master - author: Denis Chaplygin <dchaplyg(a)redhat.com>

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3282 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-z0tcz.

1 0

OST not running
by Michal Skrivanek 23 Jan '19

23 Jan '19

can someone please poke jenkins? there seems to be no machine available for OST, all is getting stuck in pending Thanks, michal

2 1

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

23 Jan '19

Failed to run project_setup.sh for: #3282 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-6zt0p.

1 0

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

23 Jan '19

Failed to run project_setup.sh for: #3282 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-9nlwk.

1 0