a6614d38dd
While debugging the ``rescue`` test functionality with ironic's tempest plugin, we discovered that if the environment suggests the agent is available, then we may enter a situation where the test can fail because paramiko prefers ssh over password authentication. This is important, because for rescue functionality in particular, it is password authentication based without the use of SSH keys, as a temporary password is generated by the services and provided to the user requesting to rescue the instance/node. Instead of trying to make an assumption that password being present means we should just disable the agent, explicitly allow the caller to specify it. Change-Id: Iefb6cb5cb80eb2b9a4307912c4d6d07c684ed70a
Team and repository tags
Tempest - The OpenStack Integration Test Suite
This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
- Documentation: https://docs.openstack.org/tempest/latest/
- Features: https://specs.openstack.org/openstack/qa-specs/#tempest
- Bugs: https://bugs.launchpad.net/tempest/
- Release Notes: https://docs.openstack.org/releasenotes/tempest
Get in touch via email. Use [tempest] in your subject.