Bug#702647: [Openstack-devel] Bug#702647: Bug#702647: test of glance-api and glance-registry still running beyond package build
On 03/10/2013 02:10 AM, Michael Tautschnig wrote: > My command line is > > pdebuild --pbuilder cowbuilder --use-pdebuild-internal > > It might be the case that the use of pdebuild-internal introduces some > additional risk of trouble - but here it might actually help to discover a > problem :-) > > Best, > Michael Hi, Thanks for all the details and answering my questions. I also use cowbuilder in my Jenkins server (but using git-buildpackage, not pdebuild), so it should be easy to check for me. This will be addressed, though I have some other important things on my todo first (more on this on another thread). Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702647: [Openstack-devel] Bug#702647: test of glance-api and glance-registry still running beyond package build
Hi Thomas, [...] > > During package build, glance-api and glance-registry are launched, but > > apparently never killed. Here is the resulting process tree after build > > completion: > > [...] > I think I have seen behavior like that, but I didn't know it was ALWAYS > the case that Glance had this trouble. So really, thanks for the report > Michael. > I can confirm that this is - at least in my setup - *always* the case (I have been trying this 5 times or so by now). > Have you tried in a cowbuilder? What kind of chroot are you talking about? > > I'm asking, because I've build glance in a cowbuilder, and it wasn't a > problem. I'm talking here about the pre-release version 2013.1~g3, which > isn't even uploaded to Debian. And I'm asking, to make sure it's only > present in the older version of Glance, so that information might help > me! :) > [...] My command line is pdebuild --pbuilder cowbuilder --use-pdebuild-internal It might be the case that the use of pdebuild-internal introduces some additional risk of trouble - but here it might actually help to discover a problem :-) Best, Michael pgpSWUbILDvgr.pgp Description: PGP signature
Bug#702647: [Openstack-devel] Bug#702647: test of glance-api and glance-registry still running beyond package build
On 03/09/2013 10:55 PM, Michael Tautschnig wrote: > Package: glance > Version: 2012.1.1-4 > Usertags: goto-cc > > During package build, glance-api and glance-registry are launched, but > apparently never killed. Here is the resulting process tree after build > completion: > > 23165 ?Ss 0:00 python > /home/mictau/build/glance/glance-2012.1.1/bin/glance-api --config-file > /tmp/test.89824/etc/api.conf > 23166 ?S 0:00 \_ /bin/sh -c logger -t "glance-api[23165]" > 23167 ?S 0:00 \_ logger -t glance-api[23165] > 23197 ?Ss 0:00 python > /home/mictau/build/glance/glance-2012.1.1/bin/glance-registry --config-file > /tmp/test.89824/etc/registry.conf > 23199 ?S 0:00 \_ /bin/sh -c logger -t "glance-registry[23197]" > 23200 ?S 0:00 \_ logger -t glance-registry[23197] > 23862 ?Ss 0:00 python > /home/mictau/build/glance/glance-2012.1.1/bin/glance-api --config-file > /tmp/test.53390/etc/api.conf > 23863 ?S 0:00 \_ /bin/sh -c logger -t "glance-api[23862]" > 23864 ?S 0:00 \_ logger -t glance-api[23862] > 23894 ?Ss 0:00 python > /home/mictau/build/glance/glance-2012.1.1/bin/glance-registry --config-file > /tmp/test.53390/etc/registry.conf > 23900 ?S 0:00 \_ /bin/sh -c logger -t "glance-registry[23894]" > 23901 ?S 0:00 \_ logger -t glance-registry[23894] > > This breaks builds inside chroots, because the build place cannot be > unmounted. > > Best, > Michael Hi, I think I have seen behavior like that, but I didn't know it was ALWAYS the case that Glance had this trouble. So really, thanks for the report Michael. Have you tried in a cowbuilder? What kind of chroot are you talking about? I'm asking, because I've build glance in a cowbuilder, and it wasn't a problem. I'm talking here about the pre-release version 2013.1~g3, which isn't even uploaded to Debian. And I'm asking, to make sure it's only present in the older version of Glance, so that information might help me! :) Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702647: test of glance-api and glance-registry still running beyond package build
Package: glance Version: 2012.1.1-4 Usertags: goto-cc During package build, glance-api and glance-registry are launched, but apparently never killed. Here is the resulting process tree after build completion: 23165 ?Ss 0:00 python /home/mictau/build/glance/glance-2012.1.1/bin/glance-api --config-file /tmp/test.89824/etc/api.conf 23166 ?S 0:00 \_ /bin/sh -c logger -t "glance-api[23165]" 23167 ?S 0:00 \_ logger -t glance-api[23165] 23197 ?Ss 0:00 python /home/mictau/build/glance/glance-2012.1.1/bin/glance-registry --config-file /tmp/test.89824/etc/registry.conf 23199 ?S 0:00 \_ /bin/sh -c logger -t "glance-registry[23197]" 23200 ?S 0:00 \_ logger -t glance-registry[23197] 23862 ?Ss 0:00 python /home/mictau/build/glance/glance-2012.1.1/bin/glance-api --config-file /tmp/test.53390/etc/api.conf 23863 ?S 0:00 \_ /bin/sh -c logger -t "glance-api[23862]" 23864 ?S 0:00 \_ logger -t glance-api[23862] 23894 ?Ss 0:00 python /home/mictau/build/glance/glance-2012.1.1/bin/glance-registry --config-file /tmp/test.53390/etc/registry.conf 23900 ?S 0:00 \_ /bin/sh -c logger -t "glance-registry[23894]" 23901 ?S 0:00 \_ logger -t glance-registry[23894] This breaks builds inside chroots, because the build place cannot be unmounted. Best, Michael pgpkBqxnc_acT.pgp Description: PGP signature
