fd25366d35
exec_command_in_pod was hanging from time to time and we've set a 10 seconds timeout waiting for a response from it. This might be too little as we very often see empty responses being returned. This commit attempts to solve the issue by setting default timeout to 60 seconds. Also the method used is changed from connect_get_namespaced_pod_exec to connect_post_namespaced_pod_exec. This is what `kubectl` uses to perform `exec`, so hopefully it'll be more reliable. Depends-On: I3bbac8e90553be9424fa0ecdb4c05e096da8f2d7 Change-Id: I49ac4d066a0bd0da3833dcbf41655f7c9e374fd9 |
||
---|---|---|
.. | ||
README.rst | ||
__init__.py | ||
base.py | ||
base_network_policy.py | ||
consts.py | ||
test_cross_ping.py | ||
test_cross_ping_multi_worker.py | ||
test_daemon.py | ||
test_ha.py | ||
test_kuryr_restart.py | ||
test_namespace.py | ||
test_network_policy.py | ||
test_npwg_multi_vif.py | ||
test_ocp_route.py | ||
test_port_pool.py | ||
test_service.py |
README.rst
What are these tests?
As stated in the tempest developer guide, scenario tests are meant to be used to test the interaction between several OpenStack services to perform a real-life use case.
In the case of the Kuryr Tempest Plugin it also involves interaction with Kubernetes pods, so its manager class includes handlers to its python bindings.
A developer using this manager would be able to perform, among others, CRUD operations with pods, alongside Kuryr-K8s added funcionality.