yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49745
[Bug 1118457] Re: Simultaneous launch of multiple instances from horizon leads to multiple LANs assigned to new tenant
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1118457
Title:
Simultaneous launch of multiple instances from horizon leads to
multiple LANs assigned to new tenant
Status in OpenStack Compute (nova):
Expired
Bug description:
Using folsom and VlanManager, if one launches multiple vm for a new
tenant/project by setting the number of instances to 4 or 5 then there
is a race condition and potentially two or more vlan/networks are
assigned to one tenant.
It seems to me that the assignment of a network to a tenant is lazy evaluated until the first instance for the project is launched. This
can be confirmed by creating a new tenant and then doing 'nova-manage network list'.
After launching the vms this is the output of 'nova-manage network list', showing the multiple vlans assigned to the same tenant:
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 172.17.0.0/24 None 172.17.0.3 None None 143 cc76e58acf6741d5a7238b74473c6a9d f43f2aab-80c1-4efe-a57a-65927b192bc5
2 172.17.1.0/24 None 172.17.1.3 None None 144 aeecc883b1a34e3cbc0ba1f5f6deae51 b0ebbe87-5554-42a2-8a2b-b68fde29e6bd
3 172.17.2.0/24 None 172.17.2.3 None None 145 aeecc883b1a34e3cbc0ba1f5f6deae51 e9a5c116-eb56-4c23-9018-6f2a2107356b
4 172.17.3.0/24 None 172.17.3.3 None None 146 dda25aeeb8cf4bb099ba7982ce05520c 51d51655-8231-4d72-b880-3bc40e6ef027
5 172.17.4.0/24 None 172.17.4.3 None None 147 dda25aeeb8cf4bb099ba7982ce05520c 073d948b-2ee2-4da2-8b90-ca47fac52854
6 172.17.5.0/24 None 172.17.5.3 None None 148 None a23fe5a0-44b6-45e8-a32b-9bb249588426
There is some discussion of the issue here:
http://lists.openstack.org/pipermail/openstack-dev/2013-February/005473.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1118457/+subscriptions