OpenStack Octavia Charm

Use of OVN provider driver unreliable on Ussuri

Bug #1927960 reported by Frode Nordahl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Octavia Charm
Fix Released
High
Frode Nordahl
OpenStack Octavia Charm 21.10

Bug Description

At Ussuri the code for the stateful Octavia OVN provider driver executes within the context of an Apache WSGI process.

The driver needs to react to network control plane events asynchronously and as you can imagine this does not work very well in a possibly short lived WSGI process.

This situation was resolved at OpenStack Victoria so we should not have enabled support for the OVN L4 provider driver at Ussuri.

I suggest we disable it in the charm at Ussuri and enable it in Victoria and onward instead.

Frode Nordahl (fnordahl)
Changed in charm-octavia:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Frode Nordahl (fnordahl)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-octavia (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-octavia/+/790554

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-octavia (master)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/790554
Committed: https://opendev.org/openstack/charm-octavia/commit/d5b9859741829adc403b8078999bbc9998ec6611
Submitter: "Zuul (22348)"
Branch: master

commit d5b9859741829adc403b8078999bbc9998ec6611
Author: Frode Nordahl <email address hidden>
Date: Mon May 10 15:16:53 2021 +0200

    Enable OVN L4 provider from Victoria onward

    The driver is unreliable at Ussuri.

    Also ensure we restart the ovn-driver-agent when configuration is
    written to disk.

    Ensure Port Security is enabled as this is a requirement for
    reliable operation of the Amphora driver also exercised by the
    functional tests.

    Enable focal/groovy-victoria gates and re-enable Ussuri OVS gate.

    Closes-Bug: #1927960
    Closes-Bug: #1927962
    Related-Bug: #1927959
    Change-Id: I1bafd9eecb83aefb425bc5286f23d47c0885ac8e

Changed in charm-octavia:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-octavia (stable/21.04)

Fix proposed to branch: stable/21.04
Review: https://review.opendev.org/c/openstack/charm-octavia/+/801253

Alex Kavanagh (ajkavanagh)
Changed in charm-octavia:
milestone: none → 21.10
Alex Kavanagh (ajkavanagh)
Changed in charm-octavia:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-octavia (stable/21.04)

Change abandoned by "Aurelien Lourot <email address hidden>" on branch: stable/21.04
Review: https://review.opendev.org/c/openstack/charm-octavia/+/801253
Reason: 21.10 has been released meanwhile

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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