Comment 4 for bug 1857365

tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps tests:

test_boot_into_disabled_port_security_network_without_secgroup
test_port_security_disable_security_group
test_port_update_new_security_group

^^ 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?

------

tempest.api.compute.admin.test_servers_on_multinodes.ServersOnMultiNodesTest.test_create_servers_on_different_hosts_with_list_of_servers

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 found this BZ regarding the same issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1566148
In that case the CI running the test was missing SameHostFilter and DifferentHostFilter, there is a link to a devstack change which enables them:
https://github.com/openstack/devstack/commit/e0d61118f198e6a46af0956902485098f78e8d26

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