^^ those 3 tests get triggered when network-feature-enabled.port_security is set to True in tempest.conf. No change happen in python-tempestconf in 2.4.0 release regarding that. The other condition which needs to be set in order to run those 3 tests is running slow tests. Is it possible that the jobs run now slow tests as well?
------
>>> May be transient issue, i saw some failure jobs but didn't find those tests failing, i found some other security_group tests failures but those tests too failed due to different host filter.
The new 2.4.0 release of python-tempestconf contains the following change: https://review.opendev.org/#/c/691573/
That change sets min_compute_nodes. The test was skipped as min_compute_nodes wasn't set by default before. If it's not desired to run it, the test should be explicitly skipped.
>> I think this can be discussed with nova team as changes might be required in recent releases as well. For now i think skipping the classes which were skipped till now needs to be completely skipped with skiplist like https://review.opendev.org/700443 was incomplete.
A year ago, the following tempest change was merged: https://review.opendev.org/#/c/570207/
Before (current state in rocky and queens) all scheduler filters were enabled by default. That got changed by the 570207 review as the test_create_servers_on_different_hosts_with_list_of_servers test requires a special filter which doesn't have to be set in nova.conf on overcloud node.
So I see 2 options here:
1. enable the filters and the test should pass
2. backport the 570207 change to rocky and queens which will result in skipping the test anyway
tempest. scenario. test_security_ groups_ basic_ops. TestSecurityGro upsBasicOps tests:
test_boot_ into_disabled_ port_security_ network_ without_ secgroup security_ disable_ security_ group update_ new_security_ group
test_port_
test_port_
^^ those 3 tests get triggered when network- feature- enabled. port_security is set to True in tempest.conf. No change happen in python-tempestconf in 2.4.0 release regarding that. The other condition which needs to be set in order to run those 3 tests is running slow tests. Is it possible that the jobs run now slow tests as well?
------
>>> May be transient issue, i saw some failure jobs but didn't find those tests failing, i found some other security_group tests failures but those tests too failed due to different host filter.
tempest. api.compute. admin.test_ servers_ on_multinodes. ServersOnMultiN odesTest. test_create_ servers_ on_different_ hosts_with_ list_of_ servers
The new 2.4.0 release of python-tempestconf contains the following change: /review. opendev. org/#/c/ 691573/
https:/
That change sets min_compute_nodes. The test was skipped as min_compute_nodes wasn't set by default before. If it's not desired to run it, the test should be explicitly skipped.
>> I think this can be discussed with nova team as changes might be required in recent releases as well. For now i think skipping the classes which were skipped till now needs to be completely skipped with skiplist like https:/ /review. opendev. org/700443 was incomplete.
I found this BZ regarding the same issue: /bugzilla. redhat. com/show_ bug.cgi? id=1566148 lter, there is a link to a devstack change which enables them: /github. com/openstack/ devstack/ commit/ e0d61118f198e6a 46af09569024850 98f78e8d26
https:/
In that case the CI running the test was missing SameHostFilter and DifferentHostFi
https:/
A year ago, the following tempest change was merged: /review. opendev. org/#/c/ 570207/ servers_ on_different_ hosts_with_ list_of_ servers test requires a special filter which doesn't have to be set in nova.conf on overcloud node.
https:/
Before (current state in rocky and queens) all scheduler filters were enabled by default. That got changed by the 570207 review as the test_create_
So I see 2 options here:
1. enable the filters and the test should pass
2. backport the 570207 change to rocky and queens which will result in skipping the test anyway