Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1726735

Summary: Load balancer resources stuck in transient statuses on a deployment stack update
Product: Red Hat OpenStack Reporter: Carlos Goncalves <cgoncalves>
Component: openstack-octaviaAssignee: Nate Johnston <njohnston>
Status: CLOSED CURRENTRELEASE QA Contact: Arieh Maron <amaron>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: gthiemon, ihrachys, lpeer, majopela, mburns, mgarciac, scohen, slinaber
Target Milestone: z12Keywords: TestOnly, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-octavia-2.1.2-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-04 11:55:01 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:

Description Carlos Goncalves 2019-07-03 15:22:50 UTC 
The Octavia Ansible playbook in tripleo-common appears to restart Octavia containers regardless if there are configuration changes. This has a negative impact as it can kill Octavia services (worker, health manager and/or housekeeping) in the middle on flows leaving LB resources stuck on PENDING_* statuses. One way that this can happen is by running a deployment stack update.
Comment 6 Lon Hohberger 2020-10-29 10:50:42 UTC 
According to our records, this should be resolved by openstack-octavia-5.0.3-0.20200725114653.68c0285.el7ost.  This build is available now.
Comment 7 Arieh Maron 2020-12-03 15:10:37 UTC 
Verified as resolved by Arieh Maron 03-Dec-2020