Merge lp:~gz/juju-core/tests_os_ssh_isolation_1144704 into lp:~juju/juju-core/trunk
Status: | Merged |
---|---|
Merged at revision: | 1063 |
Proposed branch: | lp:~gz/juju-core/tests_os_ssh_isolation_1144704 |
Merge into: | lp:~juju/juju-core/trunk |
Diff against target: |
364 lines (+89/-70) 8 files modified
environs/dummy/environs_test.go (+2/-2) environs/ec2/live_test.go (+3/-2) environs/ec2/local_test.go (+3/-3) environs/jujutest/livetests.go (+4/-4) environs/jujutest/tests.go (+23/-4) environs/openstack/config_test.go (+6/-3) environs/openstack/live_test.go (+26/-26) environs/openstack/local_test.go (+22/-26) |
To merge this branch: | bzr merge lp:~gz/juju-core/tests_os_ssh_isolation_1144704 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+154667@code.launchpad.net |
Description of the change
Make openstack tests work with no ssh public key
The juju tests are not run in a well isolated manner, particularly they will
examime the user's home directory and environment variables. This branch fixes
the issue of openstack client setup complaining of no ssh public key is found in
~/.ssh even in tests that are just using the local fake server implementations.
Following the example of how this was fixed for the EC2 tests, this is done in
an ad hoc manner by adding the 'authorized-keys' config with a fake value to
tests that hit this condition.
The complication is for live tests, we really do want to use the user's ssh key,
and the test cases and setup code are used in both cases. Some shuffling of how
suite and test case setup is done was needed to make that work.
Reviewers: mp+154667_ code.launchpad. net,
Message:
Please take a look.
Description:
Make openstack tests work with no ssh public key
The juju tests are not run in a well isolated manner, particularly they
will
examime the user's home directory and environment variables. This branch
fixes
the issue of openstack client setup complaining of no ssh public key is
found in
~/.ssh even in tests that are just using the local fake server
implementations.
Following the example of how this was fixed for the EC2 tests, this is
done in
an ad hoc manner by adding the 'authorized-keys' config with a fake
value to
tests that hit this condition.
The complication is for live tests, we really do want to use the user's
ssh key,
and the test cases and setup code are used in both cases. Some shuffling
of how
suite and test case setup is done was needed to make that work.
https:/ /code.launchpad .net/~gz/ juju-core/ tests_os_ ssh_isolation_ 1144704/ +merge/ 154667
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/7943044/
Affected files: openstack/ config_ test.go openstack/ live_test. go openstack/ local_test. go
A [revision details]
M environs/
M environs/
M environs/