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. Sudo will likely be run for some operation before running juju bootstrap. Jenkins is in the sudoers list so that it can setup the tests. In the case of an upgrade test, juju 1.16.5 is bootstrapped using sudo, then juju 1.17.1 is used to call upgrade-juju. juju 1.16.5 is always used to teardown tests; it always calls sudo. This might be an transitionary problem where the local jenv was created with 1.16.5? I add a rule to remove local.jenv before any local test starts, but the tests did not pass. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
