Issue

Octavia loadbalancers stay in OFFLINE operating status but are operational. We also were unable to see anything of relevance in health-manager.log as to status changes for the created loadbalancers.

To Reproduce Steps to reproduce the behavior:

1. (overcloud) $ openstack loadbalancer amphora list 
2. (overcloud) $ openstack loadbalancer show 
3. Check operating in output of previous command

4. operating_status

   OFFLINE

Expected behavior

• After creating the loadbalancer, we would expect the operating status to report the following after sometime;

• operating_status

  ONLINE

Bug impact

• Customer reports  LBs are operational and can access to apps running behind its floating IP assigned to LB. However LB operating_status always stays Offline.

Known workaround

• No known workaround

Additional context

• SFDC case 04197230
• Comments 34 and 41 contain reproducer information

Reproducer #2 Example

• (overcloud) $ openstack loadbalancer amphora list --loadbalancer 
• (overcloud) $ openstack loadbalancer show

• • State remains offline