yahoo-eng-team team mailing list archive

[Oleg Bondarev <obondarev@xxxxxxxxxxxx>]

Investigation on the env with the issue showed that the root cause is in
small neutron.url_timeout (or neutron_url_timeout on older versions)
nova config option.  In the described case after one node fails to
allocate port due to timeout while waiting response from neutron,
instance was scheduled to another node which allocated port one more
time. As a result neutron created two ports for the same instance.

It is recommended to increase neutron.url_timeout on envs with "slow"
neutron server.


** Changed in: neutron
       Status: Incomplete => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1418786

Title:
  more than one port got created for VM

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  If server with neutron-server service have not enough resources for
  fast processing of requests then there is a high risk of multiple port
  created for VM during scheduling/networking process.

  How to reproduce:

  Just get some environment with not so fast neutron-server service node and/or mysql server. Try to spawn bunch of VMs.
  Some of them will got two ports created (in neutron DB they will have same device_id). If the system is very slow they could get three of them. If VMs would be spawned it will have only last one which nova got from neutron and this port will be the only active one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1418786/+subscriptions