← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1870723] [NEW] vm cannot be created after a large number of vms are removed from the same node

 

Public bug reported:

vm cannot be created after a large number of virtual machines are
removed from the same node

1、create a security group, has remote security group rule
2、create 50 vms in same node(eg: node01) and use same security group created in step 1
3、delete all vms created in step 2
4、create some vms in nodeo1
5、all vms create failed. error is: Build instance <id> aborted: Failed to allocate the network(s), ...


By observing the database when creating the vm, it is found that port's L2 block has not been removed.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: api-ref

** Summary changed:

- vm cannot be created after a large number of virtual machines are removed from the same node
+ vm cannot be created after a large number of vms are removed from the same node

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

Title:
  vm cannot be created after a large number of vms are removed from the
  same node

Status in neutron:
  New

Bug description:
  vm cannot be created after a large number of virtual machines are
  removed from the same node

  1、create a security group, has remote security group rule
  2、create 50 vms in same node(eg: node01) and use same security group created in step 1
  3、delete all vms created in step 2
  4、create some vms in nodeo1
  5、all vms create failed. error is: Build instance <id> aborted: Failed to allocate the network(s), ...

  
  By observing the database when creating the vm, it is found that port's L2 block has not been removed.

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


Follow ups