Ceph » devops

Needs a link:
http://pulpito.front.sepia.ceph.com/teuthology-2014-11-09_17:18:01-upgrade:firefly-x-next-distro-basic-vps/

From http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-rpm-rhel7-amd64-basic/log.cgi?log=6977d02f0d31c453cdf554a8f1796f290c1a3b89

CXXLD ceph-mon
ar: .libs/libcephfs.a: No space left on device
ranlib: .libs/libsystest.a: No space left on device
ranlib: .libs/librados.a: No space left on device
make[3]: *** [librados.la] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** [libsystest.la] Error 1
make[3]: *** [libcephfs.la] Error 1
/bin/ld: final link failed: No space left on device
error: collect2: ld returned 1 exit status
/bin/ld: final link failed: No space left on device

Looks like we need to free up some space on gitbuilder-ceph-rpm-rhel7-amd64-basic.front.sepia.ceph.com

Disk space looks ok to me:

/dev/vda1        50G   24G   27G  48% /
devtmpfs        8.8G     0  8.8G   0% /dev
tmpfs           8.8G     0  8.8G   0% /dev/shm
tmpfs           8.8G  177M  8.6G   2% /run
tmpfs           8.8G     0  8.8G   0% /sys/fs/cgroup

How can I tell Gitbuilder to re-issue the build for 6977d02f0d31c453cdf554a8f1796f290c1a3b89 ?

When I look at the log for http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-rpm-rhel7-amd64-basic/log.cgi?log=6977d02f0d31c453cdf554a8f1796f290c1a3b89

One thing that stands out to be as bizarre is that the hash in Gitbuilder (6977d02f0d31c453cdf554a8f1796f290c1a3b89) does not match the hash of the Git commit that was built (d7a31d5f2682a0f451a6c699d25431b24a4a533d). So I'm not sure what's happened there.

The 'next' branch has moved on, to c914df2de483e55df809762e45172f034cb849e0, and that appears to have built RPMs ok. Could you re-run the teuthology tests against that?

Replying to my own post for posterity:

I figured out why those Git hashes don't align. It's bug in log.cgi. Apparently the webpage:

http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-rpm-rhel7-amd64-basic/log.cgi?log=6977d02f0d31c453cdf554a8f1796f290c1a3b89

...just shows me the latest build logs, and doesn't actually show me the logs for 6977d02f0d31c453cdf554a8f1796f290c1a3b89.