juju run --all does not work with local provider

[Aaron Bentley]

$ juju run --all uname
- MachineId: "0"
  ReturnCode: 255
  Stderr: "Permission denied (publickey,password).\r\n"
  Stdout: ""
- MachineId: "1"
  Stdout: 'Linux

'
- MachineId: "2"
  Stdout: 'Linux

'

Presumably this is caused by juju attempting to ssh into machine 0 (i.e. localhost) as ubuntu.
$ juju ssh 0
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
Permission denied (publickey,password).
ERROR subprocess encountered error code 255

[Ian Booth (wallyworld)]

For local provider, juju ssh and juju run etc have to be executed as sudo.

[Aaron Bentley (abentley)]

Sudo does not appear to help:
$ sudo juju run --all uname
[sudo] password for abentley:
- MachineId: "0"
  ReturnCode: 255
  Stderr: "Permission denied (publickey,password).\r\n"
  Stdout: ""
- MachineId: "1"
  Stdout: 'Linux

'
- MachineId: "2"
  Stdout: 'Linux

'
Even if sudo is required, juju should either automatically sudo like it does for bootstrap, or error with a clear message.

[Ian Booth (wallyworld)]

The difference with bootstrap is that the automatic sudo is part of the local provider infrastructure. juju ssh and run are generic commands that are provider independent. I don't think it will be practical to hack in an auto sudo feature for these commands. For local provider, some log files also require sudo to read; it's just how local is at the moment until user space lxc can be supported.

[Aaron Bentley (abentley)]

Can these commands even work if they're provider-independent? How would they know not to log in as "ubuntu"? (My laptop has no ubuntu user, of course.)

[Ian Booth (wallyworld)]

The containers are created with an ubuntu user. Hence juju ssh works on all providers since the creation of the ubuntu user in the running images can be assumed.

[Aaron Bentley (abentley)]

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

Machine 0 isn't *in* a container.

On 2015-03-02 09:00 AM, Ian Booth wrote:
> The containers are created with an ubuntu user. Hence juju ssh
> works on all providers since the creation of the ubuntu user in the
> running images can be assumed.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU9HRYAAoJEK84cMOcf+9hARgIAIpsbMRhrVgE/g33S1/tmGpi
ifUGTJJXX9vclUQRyOkaYfwn+cJnQe1t/ymUAlzJtF9FWK5nTp2uHCChIbc5BPtl
L2bg7oe7EDzvM0MKzHcomSyGiIUzSCANVaSc0trn0v3bfQe127QsgAkMA3p+z+yW
tKGGzuyV6GMWM1fq4X1GmSUFX6wvbTYtng3Hzzjb9+rMFi6iL3NpVkEa75yWvhyN
j6go9WaVe4A6e8EYXLHwX6bW0KkVzia1dV399sfqkdXRcZ0u4yN4v1wfrOh0QxRg
NFrNInuNjJUSlLRG0som7KiGplsyPRhopyS3n9XRtoPdfDvGWpxlooYsrznieys=
=8FGd
-----END PGP SIGNATURE-----