[OpenStack-Infra] Running devstack in a Jenkins job within an LXC container

Jay Pipes jaypipes at gmail.com
Sun Feb 16 20:18:19 UTC 2014


On Mon, 2014-02-17 at 08:16 +1300, Robert Collins wrote:
> On 15 February 2014 14:43, Jeremy Stanley <fungi at yuggoth.org> wrote:
> > On 2014-02-14 20:31:38 -0500 (-0500), Jay Pipes wrote:
> > [...]
> >> At the end you will note something about leaked file descriptors. I'm
> >> not sure if this is actually the cause of the failure of the job or not,
> > [...]
> >
> > That's typical. Jenkins thinks it should warn you if your job
> > creates any files outside the workspace since it assumes anything
> > leaking out of that sandboxed area might be unintended. Pretty much
> > all of DevStack operates outside the workspace, so it's just
> > something we generally ignore in the output.
> >
> > Chances are something returned a nonzero, probably the apt-get
> > install command. Note that open-iscsi failed to start, resulting in
> > "dpkg: error processing open-iscsi (--configure): subprocess
> > installed post-installation script returned error exit status 1". In
> > cases like these, apt-get will continue to process the remaining
> > packages but then return with a nonzero exit code once it's done.
> 
> This may be of interest:
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855
> 
> tl;dr - it's currently impossible to run a bunch of necessary commands
> in a full lxc container - you need to expose non-namespaced things.

Thanks, Rob (and Chuck Short) for your links to LXC-related oddities. I
will read through those links and see if I can make progress. If not, no
probs, I'll just switch to a non-shared-kernel VM.

Best,
-jay




More information about the OpenStack-Infra mailing list