lxc bug blocks 1.17.1 release.

Aaron Bentley aaron.bentley at canonical.com
Mon Jan 27 14:29:57 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-01-27 09:24 AM, Diogo Matsubara wrote:
> 
> 
> 
> On Mon, Jan 27, 2014 at 12:17 PM, Aaron Bentley 
> <aaron.bentley at canonical.com <mailto:aaron.bentley at canonical.com>>
> wrote:
> 
> On 14-01-27 08:29 AM, Curtis Hovey-Canonical wrote:
>> Juju 1.16.5 is run with sudo, juju 1.17.* is not.
> 
>>> juju --debug bootstrap -e local --constraints mem=2G 2>&1 |
>>> tee bootstrap.log
> 
>> ^ All tests are run as jenkins. When I manually ran this test I 
>> was jenkins via ubuntu using "sudo su". The juju was 1.17.1 made 
>> from r2265.
> 
> Don't do that.  That will trigger known bugs.  You have to ssh
> into the machine as jenkins.  Your orange key should let you do
> that directly, but you can also do "sudo su jenkins" and then "ssh 
> jenkins at localhost".
> 
> 
>> Isn't this the same as doing sudo su - jenkins ? If not, what's
>> the difference?

The difference is that because you're logged in to the instance
directly as jenkins, not su'ed from ubuntu, juju won't try to chown
your files to be owned by ubuntu.  The second ssh obfuscates the
original userid from Juju, because it's a new login.

https://bugs.launchpad.net/juju-core/+bug/1245647

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLmbWUACgkQ0F+nu1YWqI3cHgCcC+coR5chHegQjdPiEZ8C5FeO
OawAn3lBRKEvf2IE6bGU+r+5cFok8qtP
=eCso
-----END PGP SIGNATURE-----



More information about the Juju-dev mailing list