Confusing behavior of default `image_cache_manager_interval` and `instance_delete_interval`
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In all periodic tasks, an "interval" setting of 0 means that the task is executed at every run of the scheduler.
Well, all except `image_
Excerpt from Folsom's `nova/compute/
@manager.
def _run_image_
"""Run a single pass of the image cache manager."""
if FLAGS.image_
return
# ...
What is even more confusing is that the periodic command scheduler will log "Running periodic task ComputeManager.
Please make `image_
Running Folsom's python-nova on Ubuntu 12.04:
# dpkg -l python-nova
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Description
+++-===
ii python-nova 2012.2.
tags: | added: compute |
Changed in nova: | |
assignee: | nobody → Alexei Kornienko (alexei-kornienko) |
status: | New → In Progress |
summary: |
- Confusing behavior of default `image_cache_manager_interval` + Confusing behavior of default `image_cache_manager_interval` and + `instance_delete_interval` |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | Alexei Kornienko (alexei-kornienko) → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
assignee: | Davanum Srinivas (DIMS) (dims-v) → nobody |
Changed in nova: | |
status: | In Progress → Confirmed |
Changed in nova: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-1 → 2015.1.0 |
This also applies to the delete task periodic job:
if CONF.instance_ delete_ interval == 0:
return