There are hardcoded values for IP addresses that are assigned to ports that the test creates. Address 10.0.0.3 collides with DHCP address in case there are at least two controllers in tested cloud with active/active DHCP enabled. (1. controller gets address 10.0.0.2 for dhcp port, second gets 10.0.0.3) This leads to test failure when attempting to create port with 10.0.0.3 IP address because this address is already in use by the DHCP port. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/tempest/common/utils/init.py", line 89, in wrapper return f(*func_args, **func_kwargs) File "/usr/lib/python2.7/site-packages/ironic_tempest_plugin/tests/scenario/test_baremetal_multitenancy.py", line 106, in test_baremetal_multitenancy fixed_ip=fixed_ip1 File "/usr/lib/python2.7/site-packages/ironic_tempest_plugin/tests/scenario/baremetal_manager.py", line 190, in boot_instance **create_kwargs File "/usr/lib/python2.7/site-packages/ironic_tempest_plugin/manager.py", line 207, in create_server image_id=image_id, **kwargs) File "/usr/lib/python2.7/site-packages/tempest/common/compute.py", line 191, in create_test_server **kwargs) File "/usr/lib/python2.7/site-packages/tempest/lib/services/compute/servers_client.py", line 95, in create_server resp, body = self.post('servers', post_body) File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 279, in post return self.request('POST', url, extra_headers, headers, body, chunked) File "/usr/lib/python2.7/site-packages/tempest/lib/services/compute/base_compute_client.py", line 48, in request method, url, extra_headers, headers, body, chunked) File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 670, in request self._error_checker(resp, resp_body) File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 781, in _error_checker raise exceptions.BadRequest(resp_body, resp=resp) tempest.lib.exceptions.BadRequest: Bad request Details: {u'message': u'Fixed IP address 10.0.100.3 is already in use on instance dhcpf42f2830-b2ec-5a2c-93f3-e3e3328e20a3-bac1c8dc-2fa4-4891-8629-05a933124ff5.', u'code': 400}
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, 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/RHEA-2019:0045