[NETVIRT-225] SG - Delete Security group influence of existing rules Created: 31/Oct/16  Updated: 03/May/18  Resolved: 09/Dec/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: zan cohen Assignee: Aswin Suryanarayanan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive 7068_new.zip     File defect 7068-karaf_logs .zipx    
Issue Links:
Duplicate
duplicates NETVIRT-214 Multiple SGs with same rules, dissoci... Resolved
External issue ID: 7068

 Description   

1.Create 2 Security groups:
SG1 rule=Tcp 22+Tcp80-Egress
SG2 rule=Tcp 22+Tcp80-ingress

2.Lunch 2 vm's in same network and different Hosts(Each one with different SG).
As it can be seen:
First vm 10.0.123.55 assosiace with Sg1
second vm 10.0.123.56 assosiace with Sg2

3.open ssh connection from 10.0.123.55->10.0.123.56 - connection succeed.

4.create additional Sg and associate to existing vm's:
vm 10.0.123.55 assosiace with Sg3
vm 10.0.123.56 assosiace with Sg4

5.open ssh connection from 10.0.123.55->10.0.123.56 - connection succeed.
6.Deassociate SG3 AND Sg4 from relevant vm
7.open ssh connection from 10.0.123.55->10.0.123.56 - connection failed.

Notes:
*******
**see in Karaf-logs date 31/10/16
**Logs locate in \\10.0.1.216\pub\zan_cohen\Bugzila_7066



 Comments   
Comment by zan cohen [ 31/Oct/16 ]

Attachment 7068_new.zip has been added with description: Karaf logs

Comment by zan cohen [ 31/Oct/16 ]

SG3 rule=Tcp 22-Egress
SG4 rule=Tcp 22-ingress

Comment by zan cohen [ 01/Nov/16 ]

please refer to logs file "defect 7068-karaf_logs .zipx" only!!

Comment by zan cohen [ 01/Nov/16 ]

Attachment defect 7068-karaf_logs .zipx has been added with description: Karaf logs

Generated at Wed Feb 07 20:21:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.