Failed to run project_setup.sh for:
#1400 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
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/496/
Build Number: 496
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last
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/747//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
Failed to run project_setup.sh for:
#3190 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
Failed to run project_setup.sh for:
#1395 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
Change 97398,9 (ovirt-provider-ovn) 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
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgheni Dereveanchin updated OVIRT-2682:
Resolution: Done
Status: Done (was: To Do)
The change was merged,
Failed to run project_setup.sh for:
#3179 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
Failed to run project_setup.sh for:
#1392 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
Failed to run project_setup.sh for:
#252 ovirt-provider-ovn [check-merged].
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
A system test invoked by the "ovirt-master" change queue including change
97969,11 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 98009,1 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing
Change 98009,1 (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
Eitan,
How many times did you see this error?
On Mon, Feb 25, 2019 at 9:49 AM Barak Korren wrote:
> That is not the real issue, the real issue seems to be this:
>
> + sudo -n systemctl start docker
> Job for docker.service failed because the control process exited with
> error code. See
Since check-patch switched to run on containers, it might require more
knowledge in debugging errors there.
I think we should arrange a session on it for infra-owners and everyone
that wasn't involved in the project.
Gal, Barak, Daniel - please schedule a session with everyone in the infra
team
14 matches
Mail list logo
