Bug 1956827

Summary: Tempest test "test_UDP_RR_source_IP_pool_show" fails with error "'Load Balancer * is immutable and cannot be updated.'"
Product: Red Hat OpenStack Reporter: Arieh Maron <amaron>
Component: openstack-octaviaAssignee: Gregory Thiemonge <gthiemon>
Status: CLOSED NOTABUG QA Contact: Bruna Bonguardo <bbonguar>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: bhaley, gthiemon, ihrachys, lpeer, majopela, scohen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-26 15:10:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Trace of the failed test
none
stack trace of the error in this bug none

Description Arieh Maron 2021-05-04 13:46:59 UTC 
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
Comment 3 Arieh Maron 2021-05-05 07:04:26 UTC 
Created attachment 1779668 [details]
stack trace of the error in this bug
Comment 6 Arieh Maron 2021-05-05 10:50:46 UTC 
@gthiemon 
Thanks, 
Is there anyway to limit the concurrency or would longer timeouts help?
Comment 9 Arieh Maron 2021-05-09 15:54:13 UTC 
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/