yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
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/1252849

Title:
  tempest fail due to neutron cache miss

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Sounds like a regression caused by following commits:
    1. https://github.com/openstack/nova/commit/1957339df302e2da75e0dbe78b5d566194ab2c08
    2. https://github.com/openstack/nova/commit/651fac3d5d250d42e640c3ac113084bf0d2fa3b4

  The above patches causing 2 issues:
    1. tempest.api.compute.servers.test_server_actions test fail leaving the servers in ERROR state.
    2. Unable to delete those servers using nova delete.

  Tempest and compute traceback here:
    http://pastebin.com/CVjG03eV

  The patch was to disable cache refresh in allocate_for_instance,
  allocate_port_for_instance and deallocate_port_for_instance methods.
  This is breaking the nova boot process when the servers are created
  using the above tempest test. However, we could create servers using
  nova boot api, manually. It is likely because the cache is disabled
  while allocating the instance.

  The servers created using above test is left in ERROR state and we are
  unable to delete them. It is likely because the cache is disabled
  while deallocating the instance and/or port.

  NOTE:
  If we restore the @refresh_sync decorator against those methods and do not use the decorate in _get_instance_nw_info, the  the above tempest test is successful. I have not tested it when deleting the VM.

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