juju test plugin tries to bootstrap local provider with "sudo"

[Sean Feole]

Since juju 17.x , we no longer require the need to "sudo" while bootstrapping a local provider. It appears that the juju test command still attempts to do this.

juju-test INFO : Starting test run on local using Juju 1.17.4
juju-test DEBUG : Loading configuration options from testplan YAML
juju-test DEBUG : Creating a new Conductor
juju-test.conductor DEBUG : Starting a bootstrap for local, kill after 300
juju-test.conductor DEBUG : Running the following: juju bootstrap -e local
ERROR bootstrapping a local environment must not be done as root
juju-test.conductor WARNING : Could not bootstrap local, got Bootstrap returned with an exit > 0. Skipping juju-test.conductor DEBUG : Starting a bootstrap for local, kill after 300
juju-test.conductor DEBUG : Running the following: juju bootstrap -e local
ERROR bootstrapping a local environment must not be done as root
juju-test.conductor WARNING : Could not bootstrap local, got Bootstrap returned with an exit > 0. Skipping juju-test INFO : Results: 0 passed, 0 failed, 2 errored

juju-core:
  Installed: 1.17.4-0ubuntu2~ubuntu13.10.1~juju1
  Candidate: 1.17.4-0ubuntu2~ubuntu13.10.1~juju1

charm-tools:
  Installed: 1.2.10-0ubuntu1~ubuntu13.10.1~ppa1
  Candidate: 1.2.10-0ubuntu1~ubuntu13.10.1~ppa1

[Sean Feole (sfeole)]

This has been fixed, quite some time ago. Marking invalid