I have followed the below steps to reproduce the issue: 1. Created two security groups one is default security group with default rules and other one is mysecgrp with tcp & icmp rules. Below are the details: root@ash2controller:/home/ashraf2# nova secgroup-list-rules mysecgrp +-------------+-----------+---------+-----------+--------------+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-------------+-----------+---------+-----------+--------------+ | tcp | 22 | 22 | 0.0.0.0/0 | | | icmp | -1 | -1 | 0.0.0.0/0 | | +-------------+-----------+---------+-----------+--------------+ root@ash2controller:/home/ashraf2# nova secgroup-list-rules default +-------------+-----------+---------+----------+--------------+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-------------+-----------+---------+----------+--------------+ | | | | | default | | | | | | default | +-------------+-----------+---------+----------+--------------+ 2. Created a network with name mydemonet(172.52.16.0/24) and key-pair. 3. Booted VM(mydemovm) with mydemonet network and assigned default,mysecgrp security groups to it. root@ash2controller:/home/ashraf2# nova boot --flavor m1.tiny --image cirros --nic net-id=78d6ad72-04af-426d-a7ed-bb312b5aa16f --security-group default,mysecgrp --key-name mykey mydemovm 4. Able to ping and do ssh to VM interface IP(172.52.16.9) 5. Now Created one more network i.e mydemonet2(172.52.18.0/24) and attached additional interface from this subnet to the mydemovm. 6. In VM details I am able to see both the security groups & interfaces. root@ash2controller:/home/ashraf2# nova show mydemovm +--------------------------------------+----------------------------------------------------------+ | Property | Value | +--------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | ash2controller | | OS-EXT-SRV-ATTR:hypervisor_hostname | ash2controller | | OS-EXT-SRV-ATTR:instance_name | instance-00000042 | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2016-03-31T08:08:04.000000 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2016-03-31T08:07:55Z | | flavor | m1.tiny (1) | | hostId | f0613ea7aaea90fd29ab9102c3d9d4d06be5c76ff39e09e5e36445d7 | | id | a234f53e-3248-4738-9084-686dec5bfa02 | | image | cirros (a827e4a3-1daf-4aa2-b7e7-7a60b8516f85) | | key_name | mykey | | metadata | {} | | mydemonet network | 172.52.16.9 | | mydemonet2 network | 172.52.18.5 | | name | mydemovm | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | default, mysecgrp | | status | ACTIVE | | tenant_id | 97813e5271954f73a56a5122cfc8087f | | updated | 2016-03-31T08:08:05Z | | user_id | 4ae480306fd44ae880e86257359447b7 | +--------------------------------------+----------------------------------------------------------+ I am able to do ssh & ping to the demovm using first interface IP(172.52.16.9) but not with additional interface IP(172.52.18.5). Is it the same reproduction scenario behavior which is reported in the bug description. Please confirm on this.