61bfb58898
During execution it may happen, that there will be UnboundLocalError exception thrown for crd_lb_ip variable, due to unmet condition for service ip not being set in the KuryrLoadbalancerCRD. Fixed by simply defining variable. Change-Id: Ie879ba0b9b85111ec1b906d66ec48127ce8dd1f9 |
||
---|---|---|
.. | ||
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_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.