yahoo-eng-team team mailing list archive

[Alan Pevec <1171915@xxxxxxxxxxxxxxxxxx>]

0 is intentional, please see
https://github.com/openstack/nova/commit/22d7c3bb0e522503a648f279e222f595c351fba2

** Changed in: nova
       Status: New => Won't Fix

** Changed in: nova
       Status: Won't Fix => Invalid

** Also affects: nova/folsom
   Importance: Undecided
       Status: New

** Changed in: nova/folsom
       Status: New => Won't Fix

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

Title:
  Nova Compute (Folsom) has wrong default image_cache_manager_interval
  value

Status in OpenStack Compute (Nova):
  Invalid
Status in OpenStack Compute (nova) folsom series:
  Won't Fix

Bug description:
  nova/compute/manager.py need to be backported in Folsom :

  In Folsom :
  ...
  cfg.IntOpt("image_cache_manager_interval", default=0,
  ...

  In Grizzly :

  ...
  cfg.IntOpt("image_cache_manager_interval", default=2400,
  ...

  Impact : in a production environment, I ran an issue with images
  purging, since image_cache_manager_interval is set at 0 by default.

  To avoid any mistake for people using default values, I suggest to
  backport this change into Folsom.

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