Re: DNF is used on CentOS CI by default

On Mon, Jan 21, 2019 at 3:53 PM Barak Korren wrote: > > > > On Mon, 21 Jan 2019 at 12:53, Yedidyah Bar David wrote: >> >> Hi all, >> >> I now noticed that at least in [1], otopi found and used DNF on >> CentOS. Meaning, we install at least enough of dnf there to make otopi >> be able to use it.

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

oVirt infra daily report - unstable production jobs - 712

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/712//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

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

Failed to run project_setup.sh for: #2149 vdsm [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

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

Failed to run project_setup.sh for: #2147 vdsm [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

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

Failed to run project_setup.sh for: #2150 vdsm [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

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

Failed to run project_setup.sh for: #2149 vdsm [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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

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

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ehud Yonasi reassigned OVIRT-2656: -- Assignee: Ehud Yonasi (was: infra) > Upstream-sources trigger for ovirt-engine-metrics does

Jenkins build is back to normal : system-sync_mirrors-glusterfs-5-el7-x86_64 #5

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement:

Re: DNF is used on CentOS CI by default

On Mon, 21 Jan 2019 at 12:53, Yedidyah Bar David wrote: > Hi all, > > I now noticed that at least in [1], otopi found and used DNF on > CentOS. Meaning, we install at least enough of dnf there to make otopi > be able to use it. Was this done on purpose? Or is this an unplanned > result of a

DNF is used on CentOS CI by default

Hi all, I now noticed that at least in [1], otopi found and used DNF on CentOS. Meaning, we install at least enough of dnf there to make otopi be able to use it. Was this done on purpose? Or is this an unplanned result of a recent upgrade? Something else? [1]

[JIRA] (OVIRT-2658) Error when fetching upstream sources

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38871#comment-38871 ] Dafna Ron commented on OVIRT-2658: -- The error in the check-patch is: {noformat} Yum-utils package has

[JIRA] (OVIRT-2658) Error when fetching upstream sources

Shirly Radco created OVIRT-2658: --- Summary: Error when fetching upstream sources Key: OVIRT-2658 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 Project: oVirt - virtualization made easy

[CQ]: a395b96 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests

Change a395b96 (ovirt-ansible-hosted-engine-setup) 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

Build failed in Jenkins: system-sync_mirrors-glusterfs-5-el7-x86_64 #4

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38868#comment-38868 ] Shirly Radco commented on OVIRT-2656: - Hi, Is this issue fixed or still at work? Thanks, -- SHIRLY

[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt organization

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2657: - Resolution: Fixed Status: Done (was: To Do) I've created the repo under oVirt org and gave

[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt organization

sbonazzo created OVIRT-2657: --- Summary: Please import ovirt-engine-sdk-go in oVirt organization Key: OVIRT-2657 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2657 Project: oVirt - virtualization made