security groups are not applied to instance till a new instance is launched

[SongBeng]

After creating a new security group in horizon, and applying it to existing instances, I notice it is not permitting traffic still till a new instance is launched. The deployment is done using packstack with Juno release.

[narasimha18sv (narasimha18sv)]

did you check by rebooting the existing VM

[SongBeng (songbeng-lim)]

yes, I've tried shutting down and restarting the instance, it didnt take effect till a new instance is launched.

[Srilatha Tangirala (jsrilatha)]

I have tried with packsack Kilo release and was not able to reproduce the bug. I was doing the following:

 VM1
 ------------------
                IP Addresses

Private-Subnet1_Subnet2
2.2.2.10
Security Groups

SG2
ALLOW IPv6 to ::/0
ALLOW IPv4 icmp from 2.2.2.0/24
ALLOW IPv4 to 0.0.0.0/0

VM2
-------------
IP Addresses

Private-Subnet3
3.3.3.3
Security Groups

default
ALLOW IPv6 from default
ALLOW IPv4 to 0.0.0.0/0
ALLOW IPv6 to ::/0
ALLOW IPv4 from default
SG2
ALLOW IPv6 to ::/0
ALLOW IPv4 icmp from 2.2.2.0/24
ALLOW IPv4 to 0.0.0.0/0

Initially I could not ping VM1 from VM2, then I associated the following security group with VM1 then ping started working instantaneously.
SG3
ALLOW IPv4 to 0.0.0.0/0
ALLOW IPv4 icmp from 3.3.3.0/24
ALLOW IPv6 to ::/0

please let me know if the sequence of steps you used is different from what I used.

Thanks,
Srilatha.

[yujie (16189455-d)]

Could not reproduce in kilo.

[Armando Migliaccio (armando-migliaccio)]

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]