Description of problem: The following tests fail: test_port_pool_min_max_update test_port_pool_noop_update test_port_pool_update Trace for test_port_pool_noop_update: Traceback (most recent call last): File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/oslo_concurrency/lockutils.py", line 360, in inner return f(*args, **kwargs) File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/kuryr_tempest_plugin/tests/scenario/test_port_pool.py", line 286, in test_port_pool_noop_update self.assertEqual(initial_ports_num+1, new_port_list_num) File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/testcase.py", line 415, in assertEqual self.assertThat(observed, matcher, message) File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/testcase.py", line 502, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 2 != 6 Version-Release number of selected component (if applicable): v3.11.219 2020-07-01. How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Seems to be a problem with the test itself. The only tests failing are the ones trying to change the configmap and the outcome seems to be that modification is somehow not enforced. As this only applies to 3.11 since 4.x will reconcile the configmap, I'm setting the target release to 3.11. Anyway this change seems will land in kuryr-tempest-plugin.
Luis. The config map is updated but test_port_pool fails: Traceback (most recent call last): File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/oslo_concurrency/lockutils.py", line 360, in inner return f(*args, **kwargs) File "/home/stack/plugins/kuryr/kuryr_tempest_plugin/tests/scenario/test_port_pool.py", line 157, in test_port_pool self.assertEqual(num_ports_expected, updated3_port_list_num) File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/testcase.py", line 415, in assertEqual self.assertThat(observed, matcher, message) File "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/testcase.py", line 502, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 6 != 11 It seems like a problem after restarting(Deleting the controller) the kuryr controller, without the restart it works. Luis,Please let me know if you want me to open a new bug.
(In reply to Itzik Brown from comment #3) > Luis. > The config map is updated but test_port_pool fails: > > > Traceback (most recent call last): > File > "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/ > oslo_concurrency/lockutils.py", line 360, in inner > return f(*args, **kwargs) > File > "/home/stack/plugins/kuryr/kuryr_tempest_plugin/tests/scenario/ > test_port_pool.py", line 157, in test_port_pool > self.assertEqual(num_ports_expected, updated3_port_list_num) > File > "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/ > testcase.py", line 415, in assertEqual > self.assertThat(observed, matcher, message) > File > "/home/stack/.virtualenvs/.tempest/lib64/python3.6/site-packages/testtools/ > testcase.py", line 502, in assertThat > raise mismatch_error > testtools.matchers._impl.MismatchError: 6 != 11 > > It seems like a problem after restarting(Deleting the controller) the kuryr > controller, without the restart it works. > > Luis,Please let me know if you want me to open a new bug. No, we saw the problem was not that the kuryr configmap was not modified. The problem was that the controller was not being restarted, therefore the new configmap was not being used. If now you are seeing a different problem that is completely different from before. Note the test you are pasting there was passing before as that one does not require update of the config map.
I saw the problem was with adding tagging support to ensure loadbalancer cleanup (https://github.com/openshift/openshift-ansible/commit/10b3c1440cf10ed4f6b5a949011a883e027405a0). The subports created by Kuryr are tagged but the parent ports (OpenShift VM nodes) are created with Heat and not tagged, thus Kuryr skips them and the port pool recovery upon kuryr controller is broken by that. Temporal workaround is to tag the OpenShift VM ports with openshift_openstack_clusterid (by default "openshift" if not modified).
OSP13 OCP 3.11 2020-08-15.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 3.11.272 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3245