yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1633323@xxxxxxxxxxxxxxxxxx>]

[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/1633323

Title:
  [available-zone]az cachee in process make mistake

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description
  ===========
  when getting in instance's detail info, AZ info is wrong

  Steps to reproduce
  ==================
  1.
  in nova.conf, set memcached_servers = None

  2.current az info:
  nova aggregate-list
  Id name     Availability Zone
  1 cas1-agg  cas1
  modifiy az info:
  nova aggregate-update 1 cas1-agg cas2

  3.get instance az info:
  nova show ID

   
  Expected result
  ===============
  AZ info is cas2

  Actual result
  =============
  AZ info is not stable.sometimes AZ is cas1, sometimes is cas2

  Reason
  ===============
  nova-api is multi-processing. When setting memcache server to none, nova-api will cache az in process memory. But nova-api processes caches are not consistent.
  So I suggest nova-api does not cache az info in process memory.
  Related file is nova/openstack/common/memorycached.py
  Related class is Client.

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