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

Bug 1689674

Summary: Cannot recreate Octavia Load Balancer in ERROR state
Product: Red Hat OpenStack Reporter: Bruna Bonguardo <bbonguar>
Component: openstack-octaviaAssignee: Nir Magnezi <nmagnezi>
Status: CLOSED ERRATA QA Contact: Bruna Bonguardo <bbonguar>
Severity: urgent Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: cgoncalves, ihrachys, jamsmith, lpeer, majopela, rheslop, scohen, tvignaud
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)Flags: nmagnezi: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-octavia-3.0.2-0.20181219195055.ec4c88e.el7ost Doc Type: Bug Fix
Doc Text:
Prior to this update, load balancers could not be failed over when in ERROR provisioning status, after controller and computes have been rebooted. This update enables the load balancer failover.
 Story Points: ---
Clone Of:
: 1689679 (view as bug list) Environment:
Last Closed: 2019-04-30 17:51:50 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:
Bug Depends On: 1697794    
Bug Blocks: 1689679    

Description Bruna Bonguardo 2019-03-17 14:58:16 UTC 
Description of problem:

After restarting a controller node, all the Octavia Load Balancers and their respective amphorae go to an ERROR state. There is no way of bringing the Load Balancers up, without deleting and recreating them manually.


Version-Release number of selected component (if applicable):

Openstack version 14. Puddle from January 17 2019.


How reproducible: 100%


Steps to Reproduce:

1. Create an environment with one Undercloud, one Controller and one Compute.
2. Create multiple Octavia Load Balancers.
3. Restart the Controller node ~ All Load balancers and amphorae will get to a ERROR state. The controller restart will trigger a scheduling issue between the Compute and Controller nodes.
4. Restart the Compute node.

Actual results:

All EXISTING Octavia Load Balancers and Amphorae go to an ERROR state.
There is no way of bringing the Load Balancers and Amphorae back up. Even after restarting the Octavia dockers in the controller.
All NEW Load Balancers are created without errors. 

Expected results:

We should be able to RECREATE/REBUILD Load Balancers which are in ERROR state, and after the creation, the Load Balancers themselves should be in ACTIVE state after the Compute issue is resolved.
Comment 16 errata-xmlrpc 2019-04-30 17:51:50 UTC 
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/RHBA-2019:0950