Bug #17890
closedgitbuilder does not build latest Jewel packages for xenial
0%
Description
The latest Jewel commit https://github.com/ceph/ceph/commit/427f357f0eed32c9ce17590ae9303a94e8b710e7
is included in gitbuilder's Jewel package for trusty
http://gitbuilder.ceph.com/ceph-deb-trusty-x86_64-basic/ref/jewel/sha1
but not for xenial http://gitbuilder.ceph.com/ceph-deb-xenial-x86_64-basic/ref/jewel/sha1
The gitbuilder Jewel packages for xenial is used by CephFS/Manila
CI. The CI is currently broken and needs the commit to be included
in the xenial Jewel packages to unblock it.
Loic pointed out that the packages are not being built due to device
running out of space,
"Error 28 while writing to ../out/output/sha1/b124ab8b49b6708673caf6b240d73515122f8eb3.tmp/pool/main/c/ceph/ceph-common-dbg_10.2.3-469-gb124ab8-1xenial_amd64.deb: No space left on device"
Updated by Brett Niver over 7 years ago
So the situation will be resolved by rebuilding?
Updated by Loïc Dachary over 7 years ago
For the record I tried to force rebuild the "jewel" branch this morning and the issue is still here. @Brett : yes, I think the issue can be resolved by rebuilding once the underlying machine is given enough disk space.
Updated by Alfredo Deza over 7 years ago
You should no longer rely on Gitbuilders CI output. They are on their way to being turned off completely.
Please use the new system.
For Jewel you should look at the status page here: https://shaman.ceph.com/builds/ceph/jewel/
For that specific SHA1 you would look at this URL: https://shaman.ceph.com/builds/ceph/jewel/427f357f0eed32c9ce17590ae9303a94e8b710e7/
We have CentOS7, Xenial, and Trusty packages for those.
The repositories are listed here: https://shaman.ceph.com/repos/ceph/jewel/427f357f0eed32c9ce17590ae9303a94e8b710e7/
This would be the one for Xenial (linked from the status page)
Note that the repositories are destroyed after two weeks.
Updated by David Galloway over 7 years ago
- Status changed from New to Resolved
- Assignee set to David Galloway
Since I don't think we're 100% ready to retire all the gitbuilders, I increased the gitbuilder VM's disk size and forced rebuild on the 3 branches that failed as well as the commit mentioned (b124ab8b).