503 error from octavia after overcloud deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Rabi Mishra |
Bug Description
1. Standard overcloud deployment with octavia (with default ovn) using -e $THT/environmen
2. openstack loadbalancer list fails with below error.
REQ: curl -g -i -X GET http://
Starting new HTTP connection (1): 192.168.24.11:9876
http://
RESP: [503] Cache-Control: no-cache Connection: close Content-Type: text/html
RESP BODY: Omitted, Content-Type is set to text/html. Only application/json responses have their bodies logged.
Request returned failure status: 503
Service Unavailable (HTTP 503)
3. octavia api does not start and loops all the time failing to load ovn provider driver
2019-04-17 09:36:30.299 21 DEBUG octavia.api.app [-] {'"ovn"': '"Octavia OVN driver"}', '{"amphora"': '"Octavia Amphora Driver"'} _init_drivers /usr/lib/
2019-04-17 09:36:30.299 21 DEBUG octavia.api.app [-] "ovn" _init_drivers /usr/lib/
2019-04-17 09:36:30.299 21 WARNING stevedore.named [-] Could not load "ovn"
2019-04-17 09:36:30.300 21 ERROR octavia.
We seem to have added provider_driver based on neutron_driver in https:/
However, there are 2 issues with that patch
1. The octavia_api image does not have networking-ovn to have the provider driver for ovn.
2. The way we specify provider_drivers (oslo.config DictOpt) seems incorrect
Changed in tripleo: | |
milestone: | none → train-1 |
Fix proposed to branch: master /review. openstack. org/653375
Review: https:/