Bugzilla – Bug 1129274
ceph-test build failed as no OBS worker with enough disk space for ppc64le
Last modified: 2021-07-19 10:45:21 UTC
Created attachment 800107 [details]
ceph-test build failed as no worker with enough disk space for ppc64le
There are two problems:
* ceph-test build failed on obs-power8-02 (configured with disk 51200MB)
* OBS do not report failure and reschedule the build again and again.
(no build status from osc jobhist)
the manually captured build log reports:
[ 0s] obs-power8-02 started "build ceph-test.spec" at Thu Mar 14 10:12:13 UTC 2019.
[ 0s] Building ceph-test for project 'openSUSE:Factory:PowerPC' repository 'standard' arch 'ppc64le' srcmd5 'b8a3a86d6083185f1a3a653eddd7e66e'
[17769s] /.build/build-vm: line 425: echo: write error: No space left on device
[17769s] /.build/build-recipe: line 196: echo: write error: No space left on device
[17769s] obs-power8-02 failed "build ceph-test.spec" at Thu Mar 14 15:08:20 UTC 2019.
[17769s] Filesystem 1K-blocks Used Available Use% Mounted on
[17769s] /dev/vda 51605984 51589600 0 100% /
[17769s] obs-power8-02 ran out of disk space. Please try again.
[17769s] /.build/build: line 425: echo: write error: No space left on device
$osc jobhist -l5 openSUSE:Factory:PowerPC/ceph standard ppc64le
time package reason code build time worker
2018-12-19 17:51:35 ceph source change succeeded 3h 28m 3s obs-power8-01:16
2019-01-29 07:01:11 ceph new build succeeded 4h 25m 19s obs-power8-02:12
2019-01-31 16:29:56 ceph meta change failed 9h 47m 20s obs-power8-02:4
2019-02-05 01:34:47 ceph source change succeeded 4h 27m 10s obs-power8-02:10
2019-03-08 17:06:50 ceph source change succeeded 4h 17m 50s obs-power8-02:4
This is blocking release process for ppc64le as build rescheduled
I have aborted the job for now to unblock the project.
The ceph-test RPM is only needed for CI testing, so there is no clear and present need to build it for ppc64le.
Could it be disabled permanently for this architecture?
I made the following change to ceph-test.spec:
-ExclusiveArch: x86_64 aarch64 ppc64le
This should hopefully resolve the issue.
Is there an OBS sr to track ?
(In reply to Michel Normand from comment #4)
> Is there an OBS sr to track ?