[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liora Milbaum reopened OVIRT-2641: -- > mirror_mgr.sh - Build error > --- > > Key: OVIRT-2641 >

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liora Milbaum updated OVIRT-2641: - Resolution: Won't Fix Status: Done (was: To Do) > mirror_mgr.sh - Build error >

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38827#comment-38827 ] Eyal Edri commented on OVIRT-2641: -- How urgent is this really is? I prefer to reduce priority if the mirror

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

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

Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

On Sun, Jan 13, 2019 at 10:34 AM Edward Haas wrote: > > Thank you Nir. > I added an assert message to this last one. > It should not happen at all, it is very strange. > > https://gerrit.ovirt.org/#/c/96849/ > > Thanks, > Edy. > > On Sun, Jan 13, 2019 at 9:21 AM Nir Soffer wrote: > >> Another

Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

On Tue, Jan 15, 2019 at 11:15 AM Yedidyah Bar David wrote: > On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron wrote: > > > > The last ovirt-engine package ran on Jan 11th and this failure happened > on the 14th so the appliance package is suppose to be newer then the engine > and should be running

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

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

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

this is the same issue as in 4.2: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 Didi has replied to this issue and we are waiting for the maintainers of the package to review On Mon, Jan 14, 2019 at 8:57 PM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue

[JIRA] (OVIRT-2650) ovirt-master and 4.2 failing on ovirt-ansible-hosted-engine-setup

Dafna Ron created OVIRT-2650: Summary: ovirt-master and 4.2 failing on ovirt-ansible-hosted-engine-setup Key: OVIRT-2650 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 Project: oVirt -

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

Failed to run project_setup.sh for: #3161 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-2641) mirror_mgr.sh - Build error

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liora Milbaum updated OVIRT-2641: - Status: To Do (was: In Progress) > mirror_mgr.sh - Build error > --- >

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38828#comment-38828 ] Liora Milbaum commented on OVIRT-2641: -- [~eedri] It is not urgent at all > mirror_mgr.sh - Build error >

Jenkins build is back to normal : system-sync_mirrors-fedora-updates-fc29-x86_64 #197

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

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

Failed to run project_setup.sh for: #3171 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-2651) All vdsm builds fail now

Nir Soffer created OVIRT-2651: - Summary: All vdsm builds fail now Key: OVIRT-2651 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2651 Project: oVirt - virtualization made easy Issue Type:

[JIRA] (OVIRT-2651) All vdsm builds fail now

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38832#comment-38832 ] Barak Korren commented on OVIRT-2651: - [~edwardh] is this the issue we talked about today? > All vdsm

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

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

Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

On Tue, Jan 15, 2019 at 12:56 PM Nir Soffer wrote: > On Sun, Jan 13, 2019 at 10:34 AM Edward Haas wrote: > >> >> Thank you Nir. >> I added an assert message to this last one. >> It should not happen at all, it is very strange. >> >> https://gerrit.ovirt.org/#/c/96849/ >> >> Thanks, >> Edy. >>

Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

On Tue, Jan 15, 2019 at 6:28 PM Martin Perina wrote: > There is way how to replace directory from previous package version with a > symlink in new version, we are already using this in other roles. Ondro, > could you please share the details about this hack? > Ahh, sorry, I see that your are

Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

There is way how to replace directory from previous package version with a symlink in new version, we are already using this in other roles. Ondro, could you please share the details about this hack? On Tue, 15 Jan 2019, 13:24 Simone Tiraboschi > > On Tue, Jan 15, 2019 at 11:15 AM Yedidyah Bar

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

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

Re: [VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again

On Tue, Jan 15, 2019 at 8:41 PM Nir Soffer wrote: > > On Tue, Jan 15, 2019 at 12:56 PM Nir Soffer wrote: > >> On Sun, Jan 13, 2019 at 10:34 AM Edward Haas wrote: >> >>> >>> Thank you Nir. >>> I added an assert message to this last one. >>> It should not happen at all, it is very strange. >>>

All vdsm builds fail now

See https://jenkins.ovirt.org/job/vdsm_standard-check-patch/ https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1693/nodes/124/steps/376/log/?start=0

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

Failed to run project_setup.sh for: #1666 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: #1666 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: #1684 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: #1674 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: #1675 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: #1678 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: #1680 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: #1676 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: #1671 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

oVirt infra daily report - unstable production jobs - 706

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

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38834#comment-38834 ] Barak Korren commented on OVIRT-2649: - I created the following patches to iprove cleanup on slaves:

[JIRA] (OVIRT-2636) Tests failed because global_setup.sh failed

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38833#comment-38833 ] Barak Korren commented on OVIRT-2636: - I brought vm0096 back online now since the issue does not seem to

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38822#comment-38822 ] Barak Korren commented on OVIRT-2649: - I'm not sure bigger disk space is the right solution, we'll just

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38822#comment-38822 ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:11 AM: -- I'm not sure

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38823#comment-38823 ] Barak Korren commented on OVIRT-2649: - We can probably make {{slave_cleanup.sh}} take more drastic steps

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38824#comment-38824 ] Barak Korren commented on OVIRT-2649: - looking at the job logs linked above: {code} 12:17:48 Filesystem

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #196

See Changes: [Barak Korren] master_deploy: Created master deployment flow -- Started by timer [EnvInject] - Loading node environment

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38820#comment-38820 ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:07 AM: -- we usually want

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38820#comment-38820 ] Barak Korren commented on OVIRT-2649: - we ususal;y waht {{/var/cache}} to stick around since we nee the

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38820#comment-38820 ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:07 AM: -- we usually waht

[JIRA] (OVIRT-2649) Not enough space on slaves for building

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=38821#comment-38821 ] Eyal Edri commented on OVIRT-2649: -- the slave got offline automatically due to out of space. Since this only

[JIRA] (OVIRT-2652) Supporting comments on ovirt-site Blog section

Roy Golan created OVIRT-2652: Summary: Supporting comments on ovirt-site Blog section Key: OVIRT-2652 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2652 Project: oVirt - virtualization made easy

Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

The last ovirt-engine package ran on Jan 11th and this failure happened on the 14th so the appliance package is suppose to be newer then the engine and should be running fine. if this is not the case, then I suggest that the maintainers of the project see what is needed to be updated and trigger a

Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]

On Tue, Jan 15, 2019 at 11:38 AM Dafna Ron wrote: > > The last ovirt-engine package ran on Jan 11th and this failure happened on > the 14th so the appliance package is suppose to be newer then the engine and > should be running fine. > if this is not the case, then I suggest that the