Hide Forgot
Created attachment 1779381 [details] Trace of the failed test Description of problem: In OSP version 16.1 The tempest test octavia_tempest_plugin.tests.api.v2.test_pool.PoolAPITest.test_PROXY_SI_pool_delete fails with the error tempest.lib.exceptions.Conflict: Conflict with state of target resource Details: {'faultcode': 'Client', 'faultstring': 'Load Balancer **** is immutable and cannot be updated.', 'debuginfo': None} How reproducible: 100% Steps to Reproduce: Run any of the octavia-tempest-plugin tests that delete either a loadbalancer or a laodbalancer pool . Actual results: Error: tempest.lib.exceptions.Conflict: Conflict with state of target resource Details: {'faultcode': 'Client', 'faultstring': 'Load Balancer 399f04cb-16c0-41f4-b18a-13553f28a667 is immutable and cannot be updated.', 'debuginfo': None} Expected results: Success Additional info: The trace of the failed test is attached
Created attachment 1779668 [details] stack trace of the error in this bug
@gthiemon@redhat.com Thanks, Is there anyway to limit the concurrency or would longer timeouts help?
I reran the scenario with the parameter "--threads 2" instead of the default value of 4 . The scenario failed later on due to other causes but the "immutable" error was no longer occuring. The runtime for the tempest module only was 7 hours compared to 6 hours whth the dfault of "threads 4" https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/job/DFG-network-octavia-16.1_director-rhel-virthost-3cont_3comp-ipv4-geneve-actstby/11/