[Backport 1418786] more than one port got created for VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Oleg Bondarev | ||
4.1.x |
Won't Fix
|
High
|
MOS Neutron | ||
5.0.x |
Won't Fix
|
High
|
MOS Neutron | ||
5.1.x |
Won't Fix
|
High
|
MOS Neutron | ||
6.0.x |
Fix Released
|
High
|
Vitaly Sedelnik | ||
6.1.x |
Fix Released
|
High
|
Oleg Bondarev |
Bug Description
This is a backport of https:/
Original 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/
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.
Changed in mos: | |
importance: | Critical → High |
It is recommended to increase neutron.url_timeout on envs with "slow" neutron server