September 2019 - Infra - Ovirt List Archives

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

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

4 years, 7 months

1
0
0 / 0

[CQ]: 103052,2 (ovirt-host-deploy) failed "ovirt-4.3" system tests

by oVirt Jenkins

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

4 years, 7 months

1
0
0 / 0

[CQ]: 102914, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

4 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jir... ] Anton Marchukov updated OVIRT-2786: ----------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

4 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2787) connecting to ci slave as developer account

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2787?page=com.atlassian.jir... ] Anton Marchukov updated OVIRT-2787: ----------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This is generally not possible as the infrastructure is ephemeral, the way to do it is to run CI locally and/or have logs good enough to get the idea out of it. In complex cases feel free to reach us for specific case, so we can help. > connecting to ci slave as developer account > ------------------------------------------- > > Key: OVIRT-2787 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2787 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Or Shoval > Assignee: infra > > Hi Infra, > sometimes in CNV we are using CI, > and stuff fails, > it would be awesome if we can get a developer profile > that allows to connect in a restricted shell / rbash (idea by Dafna) > in order to execute commands like get pods and describe pods, > that will give hint about the problems > is it possible please ? what it involves > it can reduce lot of time and effort > thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2019