Firewall as a service v2 is not compatible with LXB

Bug #1781166 reported by Ondrej Vasko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Medium
James Denton

Bug Description

Currently FWaaS v2 is not compatible with Linux Bridges and should not be enabled when LXB is specified as L2 neutron agent. There should be a warning in documentation and condition specified in neutron playbook.

https://bugs.launchpad.net/neutron/+bug/1752006

Also I am not sure if in Queens release we follow official configuration scenario (setting proper driver, service provider, etc.)

https://docs.openstack.org/neutron/queens/admin/fwaas-v2-scenario.html

Revision history for this message
Marc Gariépy (mgariepy) wrote :

It would be nice to have doc on OSA about this.
also some logic should be added around to make sure we dont generate something not compatible.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Medium
Changed in openstack-ansible:
assignee: nobody → James Denton (james-denton)
Revision history for this message
James Denton (james-denton) wrote :

Patching incoming for docs update. There is currently no mechanism in place to determine compatible drivers/plugins, so I see that as a longer-term thing.

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_neutron (master)

Reviewed: https://review.openstack.org/636643
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_neutron/commit/?id=3dd5cbd165e89353e0e535f3f6c3924cf77eda7b
Submitter: Zuul
Branch: master

commit 3dd5cbd165e89353e0e535f3f6c3924cf77eda7b
Author: James Denton <email address hidden>
Date: Wed Feb 13 09:52:20 2019 -0500

    [docs] Update FWaaS v2 deployment scenario

    The docs currently do not mention that OVS is required for FWaaS v2.
    This patch provides a note and links to OVS deployment scenarios.

    Closes-Bug: 1781166
    Change-Id: I650b42f9a4645ed17fbfe3b5c25da9d23c6a3a52

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron stein-eol

This issue was fixed in the openstack/openstack-ansible-os_neutron stein-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron train-eol

This issue was fixed in the openstack/openstack-ansible-os_neutron train-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron ussuri-eol

This issue was fixed in the openstack/openstack-ansible-os_neutron ussuri-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron yoga-eom

This issue was fixed in the openstack/openstack-ansible-os_neutron yoga-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron victoria-eom

This issue was fixed in the openstack/openstack-ansible-os_neutron victoria-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron wallaby-eom

This issue was fixed in the openstack/openstack-ansible-os_neutron wallaby-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_neutron xena-eom

This issue was fixed in the openstack/openstack-ansible-os_neutron xena-eom release.

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.