ovn-octavia-provider: Cannot create listener due to alowed_cidrs validation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Critical
|
Unassigned | ||
Victoria |
Fix Released
|
Critical
|
Unassigned | ||
octavia |
Fix Released
|
Critical
|
Brian Haley | ||
ovn-octavia-provider (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Groovy |
Fix Released
|
Critical
|
Unassigned | ||
Hirsute |
Fix Released
|
Critical
|
Unassigned |
Bug Description
[Impact]
* Users cannot add listeners to an Octavia loadbalancer if it was created using the ovn provider
* This makes the ovn provider unusable in Victoria and will force people to use the more painful alternative of using the Amphora driver
[Test Case]
$ openstack loadbalancer create --provider ovn --vip-subnet-id f92fa6ca-
$ openstack loadbalancer show test-lb -c provisioning_status (Repeat until it shows as ACTIVE)
$ openstack loadbalancer listener create --name listener1 --protocol TCP --protocol-port 80 test-lb
Provider 'ovn' does not support a requested option: OVN provider does not support allowed_cidrs option (HTTP 501) (Request-ID: req-52a10944-
Alternatively run the focal-victoria-
[Where problems could occur]
* Problems would be isolated to the managment of octavia loadbalancers within an openstack cloud. Specifically the patch fixes the checking of the allowed_cidr option when a listener is created or updated.
[Other Info]
Changed in neutron: | |
importance: | Undecided → Critical |
description: | updated |
Changed in ovn-octavia-provider (Ubuntu Groovy): | |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in ovn-octavia-provider (Ubuntu Hirsute): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in ovn-octavia-provider (Ubuntu Hirsute): | |
status: | Triaged → Fix Released |
affects: | neutron → octavia |
Fix proposed to branch: master /review. opendev. org/753302
Review: https:/