Unable to set the default_provider_driver parameter

Bug #2023784 reported by Edwin Schripsema
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Octavia Charm
Status tracked in Trunk
2023.1
New
Undecided
Unassigned
Trunk
Triaged
High
Unassigned
Ussuri
New
Undecided
Unassigned
Victoria
New
Undecided
Unassigned
Wallaby
New
Undecided
Unassigned
Xena
New
Undecided
Unassigned
Yoga
New
Undecided
Unassigned
Zed
New
Undecided
Unassigned

Bug Description

If you only use the ovn provider with octavia (and set the parameter use_amphora=false) then the default driver still uses amphora instead of ovn.

It is working on the commandline if i specify --provider ovn, but it isn't working from horizon because the default is still amphora.

openstack loadbalancer create --vip-network-id 1073c754-f10f-40dd-8a5f-d5f7fcbc489f --name test
Provider 'amphora' is not enabled

When i set the default_provider_driver = ovn in the api_settings section in octavia.conf, then it is working again.

[api_settings]
{% if options.enable_amphora -%}
enabled_provider_drivers = amphora:The Octavia Amphora driver,ovn:Octavia OVN driver
default_provider_driver = amphora
{% else -%}
enabled_provider_drivers = ovn:Octavia OVN driver
default_provider_driver = ovn
{% endif -%}

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Yes, this looks like it should've been set before, as per the report. The OVN provider has only really been provided since ussuri, and so this should be backported through to ussuri.

I don't think an configuration option should be provided and just work from the "enabled_amphora" option as per the report above.

Changed in charm-octavia:
importance: Undecided → High
status: New → Triaged
tags: added: good-first-bug
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.