[kilo]Some instances are assigned with 2 IPs when 100 instances are launched concurrently.

Bug #1499319 reported by Xiao Li Xu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
High
Unassigned
nova-docker
New
Undecided
Unassigned

Bug Description

[Summary]
[nova-docker]Some instances are assigned with 2 IPs when 100 instances are launched concurrently.
[Topo]
Both controller and compute nodes are running on centos7.0 img: 3.10.0-229.11.1.el7.x86_64

[Reproduceable or not]
Can be reproduced, but not easily.
This issue happened when compute nodes use docker hypervisor, also happened before with QEMU.

[Recreate Steps]
1. On dashboard, create tenant a tenant with network and subnet.
2. Launch 100 instances concurrently.
3. After several minutes, check resultand found that 2 instances are assigned with 2 IPs separately.

[Log]
log on neutron serve and dhcp agent is attached.

Revision history for this message
Xiao Li Xu (xiao-li-xu) wrote :
Changed in neutron:
importance: Undecided → High
Revision history for this message
Matt Riedemann (mriedem) wrote :

The nova-docker virt driver is out of tree for nova and as far as I know no longer maintained, so please don't report issues against nova, report them against the nova-docker project and then after triage if they are nova issues add nova to the bug report.

Changed in neutron:
status: New → Invalid
Revision history for this message
Kevin Benton (kevinbenton) wrote :

This is likely an issue with the Nova-Neutron communications. IIRC if Nova times out creating a port it will request again, but Neutron may have filled the port request which will result in two ports.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.