Hello Thierry, I have pushed a fix for the upload-puppetforge role [1] and tested it in a disposable Ubuntu Xenial machine. Best regards Tobias On 01/16/2019 12:23 PM, Thierry Carrez wrote: > Puppet-OpenStack Stein M2 release job (triggered after > https://review.openstack.org/#/c/629753/ merged) failed for all modules > with errors similar to: > > zuul at openstack.org wrote: >> Build failed. >> >> - release-openstack-puppet http://logs.openstack.org/b1/b1434f41935eb5c4cb50fc5aea2b6406a6d0f63d/release/release-openstack-puppet/0c37729/ : POST_FAILURE in 2m 58s >> - announce-release announce-release : SKIPPED > This is due to the recent introduction of a puppetforge upload job: > https://review.openstack.org/#/c/627573/5/zuul.d/jobs.yaml > > That job tries to install a few gems and that fails because the ruby > header files are not available (missing ruby-dev / ruby-devel package). > Tarball upload jobs are then skipped, as well as announcement or > releases.o.o documentation. > > Solution is probably to add that missing package to the "build" > bindep.txt profile (for every affected puppet-* repository) that is > loaded in pre-run of that publication job. Currently that profile only > contains "puppet" and that stops short of installing the ruby > development header package (at least on Ubuntu hosts). > > Once that's done, I recommend pushing a new Stein release for > Puppet-OpenStack (similar to https://review.openstack.org/#/c/629753/, > bumping .Z for all packages) so that we can test that it properly works > before end-of-release crush. >