| 2020-11-26 16:08:06 |
Dan MacDonald |
description |
We have re-installed the openstack-telemetry-bionic-train bundle with the octavia overlay but this time I was careful to set the openstack-origin settings in the overlay to match, which is where we went wrong last time. Unfortunately we are still unable to create loadbalancers.
The command we are trying to run (as the Openstack admin user) is:
$ openstack loadbalancer create --name lb1 --vip-subnet-id internal_subnet
We get told its being deployed, but shortly after if I run:
$ openstack loadbalancer show lb1
and we get a
provisioning_status | ERROR
Logs to follow... |
We have re-installed the openstack-telemetry-bionic-train bundle with the octavia overlay but this time I was careful to set the openstack-origin settings in the overlay to match, which is where we went wrong last time. Unfortunately we are still unable to create loadbalancers.
The command we are trying to run (as the Openstack admin user) is:
$ openstack loadbalancer create --name lb1 --vip-subnet-id internal_subnet
We get told its being deployed, but shortly after if I run:
$ openstack loadbalancer show lb1
and we get a
provisioning_status | ERROR
The octavia health manager log makes it out to be a database issue:
no such table: amphora_health |
|
