OpenStack Compute (nova)

Nova Compute (Folsom) has wrong default image_cache_manager_interval value

  1. Series folsom
  2. Bug #1171915
Bug #1171915 reported by Emilien Macchi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
Folsom
Won't Fix
Undecided
Unassigned

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.

See original description
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/folsom)

Fix proposed to branch: stable/folsom
Review: https://review.openstack.org/27360

Emilien Macchi (emilienm)
description: updated
Revision history for this message
Alan Pevec (apevec) wrote :

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

Changed in nova:
status: New → Won't Fix
status: Won't Fix → Invalid
Revision history for this message
Alvaro Lopez (aloga) wrote :

This is also stated in the release notes: https://wiki.openstack.org/wiki/ReleaseNotes/Folsom#OpenStack_Compute_.28Nova.29

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.