Instance is getting 2 ports attached during launching with one of which is in down status

[AEmelyanenko]

[Test process]
1. launch an instance in horizon or via API
2. select image, network, security rule...etc
[Test result]:
1.2 IP addresses are shown to be attached to the created instance(eg:10.156.95.47 and 10.156.95.48)
2.go to network tab and check ports: port 10.156.95.47 is in status down while port 10.156.95.48 is in status up(both are up in admin status)
3.10.156.95.48 is actually assigned to the instance

I am using openstack mitaka. This happens only with internal networks and not with external-provider ones. Frequency is about 2/3 launches. I am not using any OVS tool to configure the network. FYI. This issue won't occur if you launch instances with CLI. It happens only when using horizon or API.

[John Davidge (john-davidge)]

Please provide your neutron.conf and neutron server logs, and describe your network topology so that the issue can be recreated. See [1]. Thanks.

[1] http://docs.openstack.org/developer/neutron/policies/bugs.html#bug-report-template

[Swetha G (swethamohan318)]

I'm trying to reproduce the above mentioned bug in mitaka version, I have created a new instance and assigned a network(subnet: 10.156.95.0/24 and IP: 10.156.95.3) to the instance from Horizon but only one port is getting assigned(status being UP) to it even in case of launching the instance for about 4-5 times.

Point 3 talks about the actual assignment of IP to the instance which is not very clear.

Few points mentioned are not enough to reproduce the issue so, Can you please provide us with your network topology and the need to have a second port belonging to the same network as only one port is usually tagged to each VM on a single network.

[Martynov Aleksey (alemartynov)]

I had the same problem. while creating instance it receives 2 or 3 of an internal subnet address.

root@node-21:~# openstack flavor list
+--------------------------------------+-----------+-------+------+-----------+-------+-----------+
| ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public |
+--------------------------------------+-----------+-------+------+-----------+-------+-----------+
| 1 | m1.tiny | 512 | 1 | 0 | 1 | True |
| 2 | m1.small | 2048 | 20 | 0 | 1 | True |
| 3 | m1.medium | 4096 | 40 | 0 | 2 | True |
| 4 | m1.large | 8192 | 80 | 0 | 4 | True |
| 5 | m1.xlarge | 16384 | 160 | 0 | 8 | True |
| 7cb1e2fd-7386-401d-989f-fe3bf125e53f | test250G | 8192 | 250 | 0 | 8 | True |
| e5a14836-ab19-4c65-a90a-390060c016d7 | m1.micro | 64 | 0 | 0 | 1 | True |
+--------------------------------------+-----------+-------+------+-----------+-------+-----------+
root@node-21:~# openstack image list
+--------------------------------------+---------------------------------------------------+--------+
| ID | Name | Status |
+--------------------------------------+---------------------------------------------------+--------+
| 20c87a52-d32a-4edb-8d27-28fe6a699053 | windows_server_2012_r2_standard_eval_kvm_20151021 | active |
| f33139c6-ed48-42c3-9b52-a63b9a733045 | WindowsServer2012 | active |
| 98beaace-7dc5-4057-b616-c2c6664b8ac2 | Centos7 | active |
| 67281fd0-6e9d-45fc-8c15-b544e90da464 | TestVM | active |
+--------------------------------------+---------------------------------------------------+--------+
root@node-21:~# openstack network list
+--------------------------------------+-----------------------------+--------------------------------------+
| ID | Name | Subnets |
+--------------------------------------+-----------------------------+--------------------------------------+
| dedf97fe-e2c5-4052-9b1f-fa467e659e2d | admin_floating_internal_net | 592a04f4-96cd-43e9-9e3c-6496794c4370 |
| e654054b-e26e-4a05-b4bf-d6192ebaac11 | internal | 208d3eb1-56cf-4c2c-8ca9-217413106edb |
| 387ebc48-b208-4823-b291-027104d8d38e | admin_floating_net | b00fbd76-b3b9-42cd-869f-8526d1dbb43b |
| 21866905-bb8a-4c98-9fca-d2234359a197 | internal2 | 8f8ce0cd-eb81-4a3d-a362-61c016374561 |
| 3178dfca-4e75-4eb9-8754-a9f74dc349b5 | test1 | 815fccc4-ae43-41d2-ac99-ccef00c55e34 |
| 3dced17f-11b8-4a40-b724-db27ae2f86b7 | internal | 45397986-0136-47c4-bfe1-57d8a72e3cc8 |
| 3ed20676-01d4-49f2-92f9-eaf3ef8f3c42 | internal | 975266f4-0...

[Martynov Aleksey (alemartynov)]

This error I have no matter how I create an instance (CLI, API, Horizon)

[Swetha G (swethamohan318)]

hi Martynov,

can you please share the port show output.

[Martynov Aleksey (alemartynov)]

You mean the list of network ports?

[Swetha G (swethamohan318)]

hi Martynov,
We are not able to reproduce the issue. We have not observed two ports/two ips configured after launching a virtual machine with single subnet given as input through CLI/Horizon.
We tried to reproduce this scenario with openstack mitaka environmet (neutron version - 8.3.1).Please provide the neutron version in your environment and suggest if we have missed any configuration to reproduce the bug.