On active standby configuration: We disabled the MASTER management port in order to block heartbit messages and trigger failover. The LB goes to error state, new backup amphora is not created, the backup amphora ( which is now functional ) is still shown as BACKUP (overcloud) [stack@undercloud-0 ~]$ openstack loadbalancer amphora list | grep 192.168.1.16 | 5f48afa4-8d58-4960-998e-c714d10ab21f | 7bf8921e-6d37-4667-82c3-6b3ae3410af8 | ALLOCATED | MASTER | 192.168.199.51 | 192.168.1.16 | | e232e520-4bd5-403c-880a-361a54990df8 | 7bf8921e-6d37-4667-82c3-6b3ae3410af8 | ALLOCATED | BACKUP | 192.168.199.56 | 192.168.1.16 | (overcloud) [stack@undercloud-0 ~]$ openstack port list | grep 192.168.199.51 | 1671769a-a790-4c56-8d97-d102d2630052 | | fa:16:3e:62:c7:32 | ip_address='192.168.199.51', subnet_id='06096d99-a0bc-4533-a6c8-f8824dddbf2e' | ACTIVE | (overcloud) [stack@undercloud-0 ~]$ openstack port set 1671769a-a790-4c56-8d97-d102d2630052 --disable After port disabling: (overcloud) [stack@undercloud-0 ~]$ openstack loadbalancer amphora list | grep 192.168.1.16 | e232e520-4bd5-403c-880a-361a54990df8 | 7bf8921e-6d37-4667-82c3-6b3ae3410af8 | ALLOCATED | BACKUP | 192.168.199.56 | 192.168.1.16 | 2018-05-14 14:11:51.038 22 ERROR octavia.controller.worker.controller_worker [req-94d8360b-097b-44d0-a9aa-22fb363a353a - 64ba63c12a9a46288fd4623295d81bc0 - - -] Failover exception: failed to detect a valid IP address from None: AddrFormatError: failed to detect a valid IP address from None 2018-05-14 14:11:51.060 22 INFO octavia.controller.healthmanager.health_manager [-] Attempted 1 failovers of amphora 2018-05-14 14:11:51.060 22 INFO octavia.controller.healthmanager.health_manager [-] Failed at 1 failovers of amphora 2018-05-14 14:11:51.061 22 INFO octavia.controller.healthmanager.health_manager [-] Cancelled 0 failovers of amphora 2018-05-14 14:11:51.061 22 INFO octavia.controller.healthmanager.health_manager [-] Successfully completed 0 failovers of amphora ******* Traffic is still handled properly.
This issue turned out to be caused by a misconfiguration of Octavia by the deployment tool (TripleO) that is only setting [controller_worker]/amp_boot_network_list in the worker where is should also have been set to the health manager. An amphora instance (Nova instance) was created but did not get a Neutron port created and attached to the lb-mgmt-net. A fix is required in tripleo-common. Still, Octavia should validate and error on configuration parameters with no default values to prevent cases like this.
(In reply to Carlos Goncalves from comment #2) > Still, Octavia should validate and error on configuration parameters with no > default values to prevent cases like this. https://review.openstack.org/#/c/595578/
*** Bug 1641827 has been marked as a duplicate of this bug. ***
Is there a workaround until the issue is fixed? maybe some manual configuration in "health manager"(octavia-health-manager/manager-post-deploy.conf) on all controllers?
Set [controller_worker]/amp_boot_network_list and [controller_worker]/amp_secgroup_list in the configuration file of the health manager on all controllers and restart the container.
(In reply to Carlos Goncalves from comment #7) > Set [controller_worker]/amp_boot_network_list and > [controller_worker]/amp_secgroup_list in the configuration file of the > health manager on all controllers and restart the container. Thanks, Carlos. I have made the changes. But, unfortunately, I am facing different issue while re-creating amphora instances. I have created a support case with Red Hat.
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:0448
*** Bug 1576434 has been marked as a duplicate of this bug. ***