The method ``get_ml2_conf_file`` now uses the configuration option
"ml2_plugin_config" instead of the hardcoded default value
"/etc/neutron/plugins/ml2/ml2_conf.ini"
Change-Id: Ib749d3b35ebaf030375160ebdc63b2ec4f73b959
This method checks if the Neutron API replies to a generic command
("agent list").
Related-Bug: #OSPRH-2460
Change-Id: I7982bb130e4a8ef7495e6243f656cc4095d35db8
A new target_state parameter was introduced into
remote_service_action() function in order to make sure that
a service reached the expected state.
Change-Id: I6fe09ffa86c7cbc703db56a7b72d0cf90b42f9f4
The use of retry decorator is easy and tempting,
many test methods may find various issues, therefore raising exceptions,
this change forces specific failure to be targeted by retry decorator
in order to avoid dismissing other exceptions which require a fix.
This is done by an obligatory regex, which validates
the exception caught and dismissed has the intended assertion message.
There is optional exception type argument, in order to let other
unexpected exceptions to be raised and fail the test.
Change-Id: Ib9a17d8c6c8778adf546c610dd070c14aff45ecd
Since some tests can be disruptive and can break some important
nodes an option for using only safe nodes was introduced.
With this option enabled, tests that are doing disruptive actions
will not use OSP controller nodes for this but will retry
to create objects for testing on a safer node. The option is
enabled by default.
In order to make test_l3ha_reboot_node to work properly,
discover_nodes() was changed to support nodes rescan when there
are shut off nodes.
test_l3ha_bring_down_interface was changed to use
node_tenant_interface defined in config file instead of letting
the test to discover it.
Changed default value for hypervisor_host to match the
current value used on environments deployed by ci-framework.
Moved all power operations functions to a separate class that
disruptive tests should inherit from.
Fixed incorrect calls of find_host_virsh_name by
adding required parameter and some other fixes in power
operations functions.
Change-Id: Iafe9b0210972e0c59529c4a09edbe11d68f91514
This patch adds a decorator for those functions that we want to
evaluate more than once in case of an assertion failure. Some
scenario tests are conditioned by the stability of the VM or
interfaces after their creation to obtain bandwidth measurements
according to QoS criteria. For these tests, this decorator allows
for multiple evaluations seeking stability in the measurements
Co-Authored-By: froyo@redhat.com
Change-Id: I4c562a97ff958e8c15408f3d06c54c24e9a2f1fb
Moved tests from the downstream plugin with minimal changes.
Setup function changed significantly in order to support
environments where routers can be scheduled on compute nodes.
Base _create_server function was changed to support spawning
a VM on a specific host or any host excluding list of hosts.
The tests are supported currently only on environments where ovn
routers are located on compute or standalone networker nodes.
Test that performs shutting down a node is required this
patch [1].
Also:
Since _create_server return value was changed (simplified),
adjusted some qos tests that could be affected.
Removed redundant 'return None' statements from some base functions.
[1] https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/913851
Change-Id: Ic7d46a9a432089f1cd1a30af7639e9824e464c6d
This patch contains a workaround for one of extra dhcp opts test,
test_extra_dhcp_opts_disabled_enabled_dhcp4, that uses a strict
regex for getting domain_name between 'search' and eand of the line.
In some cases the test is failing because of an extra entry 'n'
before the end of the line. This still should be investigated.
Meanwhile we apply a workaround in order to unblock the gates.
The workaround makes the regex less strict and still checks for
a proper value of the domain_name.
This patch also handles 2 comments from the previous patch.
Change-Id: Icb65bd5aefab7d23b93f148502667c8c4e62bdc2
Tests moved from downstream plugin with minimal adjustments.
These tests require nmcli inside the server so advanced image
changed to rocky-9 cloud image. Other alternative, e.g. centos-9
does not have a default user and requires additional customization
for setting the user.
Additionally, moved utils.py and constants.py.
From config.py and base.py only relevant subset of code moved.
Change-Id: I6b538c13a15e94d072091b3218b2cd48ff20a70c
