On 26/01/14 19:28, Andrew Wilkins wrote: > On Sat, Jan 25, 2014 at 11:17 PM, Curtis Hovey-Canonical > <cur...@canonical.com <mailto:cur...@canonical.com>> wrote: > CI has not passed local upgrade to 1.17.1 and deploy with 1.17.1 tests > since lp:juju-core r2248. The next revision tested was 2253 (a lot of > revs landed while CI was retesting intermittent failures) > > CI sees this on when is uses 1.17.1 juju to boostrap: > > juju --debug bootstrap -e local --constraints mem=2G 2>&1 | tee > bootstrap.log > 2014-01-25 14:51:09 DEBUG juju.environs.configstore disk.go:77 Making > /var/lib/jenkins/juju-ci/environments > 2014-01-25 14:51:09 DEBUG juju.environs.configstore disk.go:67 Making > /var/lib/jenkins/juju-ci/environments/local.jenv owned by 1000:1000 > 2014-01-25 14:51:09 ERROR juju.cmd supercommand.go:294 cannot create > new info for environment "local": chown > /var/lib/jenkins/juju-ci/environments/local.jenv: operation not > permitted > > > This looks like it's still running under sudo. Is that the case? (I see > it's not in the command line, but is this a script that is run under sudo?) > The "Making ... owned by 1000:1000" line shouldn't be there.
OR... the env vars are set even though the user isn't using sudo, or the sudo has been used run the tarmac script as a different user. Whatever it is, we shouldn't need this any more. I'll submit a proposal Monday morning to clean this up. Tim -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev