Re: [Rdo-list] fatal: The remote end hung up unexpectedly

On 10/13/2015 03:30 AM, Udi Kalifon wrote: > I failed during build images in the RDO test day: > > /var/tmp/image.Hu0HkfDD/mnt/opt/stack/puppet-modules/tempest ~/images > From > /home/stack/.cache/image-create/source-repositories/puppet_tempest_2aa8dee360256cbbbbc450f20322094249aa9dba > * [new branch] master -> fetch_master > HEAD is now at 09b2b5c Try to use zuul-cloner to prepare fixtures > ~/images > 0+1 records in > 0+1 records out > 34 bytes (34 B) copied, 7.9125e-05 s, 430 kB/s > Caching puppetlabs-vcsrepo from > https://github.com/puppetlabs/puppetlabs-vcsrepo.git in > /home/stack/.cache/image-create/source-repositories/puppetlabs_vcsrepo_23ad1fc998579fd9683437046883d2cbdc42d3e3 > Cloning into > '/home/stack/.cache/image-create/source-repositories/puppetlabs_vcsrepo_23ad1fc998579fd9683437046883d2cbdc42d3e3.tmp'... > error: RPC failed; result=7, HTTP code = 0 > fatal: The remote end hung up unexpectedly That's typically a transient github problem. There's a reason upstream infra stopped using github in their CI jobs. Why are we pulling the puppet modules from there anyway though? Is OPM in RDO not new enough?

> > Has anyone ever seen an issue like this ? > > Thanks, > Udi. _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscribe(a)redhat.com