Bug 2143941 - Creating octavia loadbalancer fails due to openflow rules not being matched when port security enabled on healthmanager port in octavia-worker
Summary: Creating octavia loadbalancer fails due to openflow rules not being matched w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 2081773
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-18 12:50 UTC by Randy Rubins
Modified: 2023-01-25 13:17 UTC (History)
11 users (show)

Fixed In Version: openvswitch2.15-2.15.0-126.el8fdp.x86_64
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-25 13:16:19 UTC
Target Upstream Version:
Embargoed:
rrubins: needinfo-
ralonso: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20291 0 None None None 2022-11-18 12:54:05 UTC

Description Randy Rubins 2022-11-18 12:50:18 UTC
Description of problem:
Creating octavia loadbalancer fails due to openflow rules not being matched when port security enabled on healthmanager port in octavia-worker.  egress traffic from octavia-worker does not reach amphora on tcp/9443.

Version-Release number of selected component (if applicable):
OSP 16.2, openstack-octavia-worker-5.1.3-2.20220328185156.el8ost

How reproducible:
With openvswitch native firewall and port-security enabled on octavia-worker (o-hm) port, the creation of load balancer does not complete and errors out (see below).  Removing port-security on that port enables loadbalancer to be created.

Steps to Reproduce:
1. create loadbalancer with port security enabled (ovs-fw) on o-hm port
2. traffic unable to egress/reach amphora instance on tcp/9443
3. only entirely removing port-security resolves the issue.  If security group rules are adjusted to allow all egress tcp/udp traffic from that port, it still does not resolve the issue.

Actual results:
Failure in ovs-fw / openflow rules matching cause dropped packets and octavia loadbalancer creation fails.

Expected results:
Openflow rules should be matched and egress should be allowed.

Additional info:

Comment 11 Randy Rubins 2023-01-25 13:16:19 UTC
Thank you! This can be closed based on comment #6.


Note You need to log in before you can comment on or make changes to this bug.