Some traffic does not work if the OVS flows to permit custom ethertypes
are not set on the base egress table. If the rule is added to the base
egress table then both ingress and egress work properly. Also move
initialization code to the function to initialize egress.
Related-Bug: #1832758
Change-Id: Ia312fe75df58723bf41804eec4bd918d223bd60c
(cherry picked from commit fb859966f79fc0f4fbb2c2ea3c0e6b4c17a9704f)
Reviewed: https:/ /review. opendev. org/686215 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=9d04e38e867 9c3f87c364bc6c9 e39b43dfb959b9
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 9d04e38e8679c3f 87c364bc6c9e39b 43dfb959b9
Author: Nate Johnston <email address hidden>
Date: Thu Aug 22 10:13:00 2019 -0400
OVS flows for custom ethertypes must be on EGRESS
Some traffic does not work if the OVS flows to permit custom ethertypes
are not set on the base egress table. If the rule is added to the base
egress table then both ingress and egress work properly. Also move
initialization code to the function to initialize egress.
Related-Bug: #1832758 3bf41804eec4bd9 18d223bd60c 4fbb2c2ea3c0e6b 4c17a9704f)
Change-Id: Ia312fe75df5872
(cherry picked from commit fb859966f79fc0f