Created attachment 1493980 [details] Octavia worker log Description of problem: When creating a new load balancer, Octavia fails to acquire a VIP, resulting in a failure of the load balancer creation Version-Release number of selected component (if applicable): - RHOSP 13 - composable Octavia - octavia-api on controllers, octavia-worker, octavia-healthmanager and octavia-housekeeping manager on are installed on the networker node. How reproducible: Steps to Reproduce: 1.Create a private network + subnet 2. # openstack loadbalancer create --name lb1 --vip-subnet-id subnet1 3. list load-balancers, the new load balancer will go on ERROR state (logs from '/var/log/containers/octavia/worker.log' attached) Actual results: - VIP is failed to be acquired Expected results: Load balancer successfully created Additional notes: Composable Octavia isn't officially supported in OSP 13.
Could you please attach sosreports from controller and networker nodes (including Nova and Neutron logs)? Does it work creating a regular Nova instance connected to the same subnet?
Problem is due to mixed network drivers being used in different services. The API isn't set with one so defaults to noop_driver, while worker service is set to use allowed_address_pairs_driver. I was able to create a load balancer after setting network_driver=allowed_address_pairs_driver in the octavia_api containers.
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:0068