This bug was fixed in the package neutron - 2:14.0.0~rc1-0ubuntu2~cloud0
---------------
neutron (2:14.0.0~rc1-0ubuntu2~cloud0) bionic-stein; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:14.0.0~rc1-0ubuntu2) disco; urgency=medium
.
* d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream
to prevent neutron ovs agent from crashing due to creation of two
security groups that both use the same remote security group, where
the first group's port range is a subset of the second (LP: #1813007).
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1813007
Title:
[SRU] Unable to install new flows on compute nodes when having broken
security group rules
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive pike series:
Fix Committed
Status in Ubuntu Cloud Archive queens series:
Fix Committed
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Fix Released
Status in neutron:
Fix Released
Status in OpenStack Security Advisory:
Incomplete
Status in neutron package in Ubuntu:
Fix Committed
Status in neutron source package in Bionic:
Fix Committed
Status in neutron source package in Cosmic:
Fix Committed
Status in neutron source package in Disco:
Fix Committed
Bug description:
It appears that we have found that neutron-openvswitch-agent appears to have
a bug where two security group rules that have two different port ranges that
overlap tied to the same parent security group will cause neutron to not be
able to configure networks on the compute nodes where those security groups are
present.
Those are the broken security rules:
https://pastebin.canonical.com/p/wSy8RSXt85/
Here is the log when we discovered the issue:
https://pastebin.canonical.com/p/wvFKjNWydr/
Ubuntu SRU Details
------------------
[Impact]
Neutron openvswitch agent crashes due to creation of two security groups that
both use the same remote security group, where the first group doesn't define a
port range and the second one does (one is a subset of the other; specifying no
port range is the same as a full port range).
[Test case]
See comment #18 below.
[Regression Potential]
The fix is fairly minimal and has landed upstream in master branch. It has
therefore passed all unit and function tests that get run in the upstream gate
and has been reviewed by upstream neutron core reviewers. This all helps to
minimize the regression potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
