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.
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.
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@ash2contro ller:/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@ash2contro ller:/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@ash2contro ller:/home/ ashraf2# nova boot --flavor m1.tiny --image cirros --nic net-id= 78d6ad72- 04af-426d- a7ed-bb312b5aa1 6f --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@ash2contro ller:/home/ ashraf2# nova show mydemovm ------- ------- ------- ------- ----+-- ------- ------- ------- ------- ------- ------- ------- ------- + ------- ------- ------- ------- ----+-- ------- ------- ------- ------- ------- ------- ------- ------- + AZ:availability _zone | nova | SRV-ATTR: host | ash2controller | SRV-ATTR: hypervisor_ hostname | ash2controller | SRV-ATTR: instance_ name | instance-00000042 | STS:power_ state | 1 | STS:task_ state | - | USG:launched_ at | 2016-03- 31T08:08: 04.000000 | USG:terminated_ at | - | 31T08:07: 55Z | d29ab9102c3d9d4 d06be5c76ff39e0 9e5e36445d7 | 3248-4738- 9084-686dec5bfa 02 | 1daf-4aa2- b7e7-7a60b8516f 85) | volumes: volumes_ attached | [] | 3a56a5122cfc808 7f | 31T08:08: 05Z | 880e86257359447 b7 | ------- ------- ------- ------- ----+-- ------- ------- ------- ------- ------- ------- ------- ------- +
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | active |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2016-03-
| flavor | m1.tiny (1) |
| hostId | f0613ea7aaea90f
| id | a234f53e-
| image | cirros (a827e4a3-
| key_name | mykey |
| metadata | {} |
| mydemonet network | 172.52.16.9 |
| mydemonet2 network | 172.52.18.5 |
| name | mydemovm |
| os-extended-
| progress | 0 |
| security_groups | default, mysecgrp |
| status | ACTIVE |
| tenant_id | 97813e5271954f7
| updated | 2016-03-
| user_id | 4ae480306fd44ae
+------
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.