yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81644
[Bug 1862703] Re: Neutron remote security group does not work
Reviewed: https://review.opendev.org/707248
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6dbba8d5ce18805a6f104782510c055017267435
Submitter: Zuul
Branch: master
commit 6dbba8d5ce18805a6f104782510c055017267435
Author: Hang Yang <hangyang@xxxxxxxxxxxxxxxx>
Date: Tue Feb 11 12:38:25 2020 -0800
Check SG members instead of ports to skip flow update
Security group can have a state of empty ports but non-empty members. So
we need skip the flow update only when members dict is empty.
Change-Id: I429edb3d2dea5fa97441909b4d2c776f97f0516f
Closes-Bug: #1862703
Related-Bug: #1854131
** Changed in: neutron
Status: In Progress => 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/1862703
Title:
Neutron remote security group does not work
Status in neutron:
Fix Released
Bug description:
Steps to reproduce the issue using Neutron Rocky with OVS:
# create bastion-sec-grp to allow ssh from anywhere
openstack security group create bastion-sec-grp
openstack security group rule create --ethertype=IPv4 --protocol tcp --remote-ip 0.0.0.0/0 --ingress --dst-port=22 bastion-sec-grp
# create application-sec-grp
openstack security group create application-sec-grp
# Allow ssh to egress from the bastion group to the application group
openstack security group rule create --ethertype=IPv4 --protocol tcp --remote-group application-sec-grp --egress --dst-port=22 bastion-sec-grp
# Allow ssh to ingress to the application group from the bastion group
openstack security group rule create --ethertype=IPv4 --protocol tcp --remote-group bastion-sec-grp --ingress --dst-port=22 application-sec-grp
# create servers and associate with security groups
openstack server create --wait --image rhel7 --flavor small --security-group bastion-sec-grp bastion-server
openstack server create --wait --image rhel7 --flavor small --security-group application-sec-grp application-server
After boot, bastion-server and application-server are landed on
different HVs and we can ssh to bastion-server but cannot ssh to
application-server from there. Neutron debug log from application-
server's HV shows:
2020-02-05 22:57:05,825 DEBUG
[neutron.agent.linux.openvswitch_firewall.firewall]
/opt/openstack/venv/neutron/lib/python2.7/site-
packages/neutron/agent/linux/openvswitch_firewall/firewall.py:_build_addr_conj_id_map:297
No member for SG <BASTION_SEC_GRP_ID>
Suspect this is related to: https://bugs.launchpad.net/neutron/+bug/1854131 and after reverting the change https://review.opendev.org/#/c/696976/ locally then remote security group started to work again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1862703/+subscriptions
References