Preventing duplicate cron job executions for glance-cache-pruner

Bug #1755377 reported by Alexander Dobdin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Alexander Dobdin

Bug Description

The queue of jobs keeps increasing every half-an-hour i.e a new process is created irrespective of the old process ending on a particular environment. This has lead to High CPU load alarms

Fuel should add lock file for glance-cache-pruner to the cron job like the following

/usr/bin/flock --nonblock /tmp/glance-cache-pruner.lock glance-cache-pruner

Changed in fuel:
importance: Undecided → High
Changed in fuel:
milestone: none → 9.2-mu-5
Revision history for this message
Alexander Rubtsov (arubtsov) wrote :

sla2 for 9.0-updates

Changed in fuel:
importance: High → Medium
tags: added: sla2
Changed in fuel:
assignee: nobody → Oleksiy Molchanov (omolchanov)
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

This script should not be executed for such a long time. Can you run it manually and provide some debug here?

Changed in fuel:
assignee: Oleksiy Molchanov (omolchanov) → Alexander Dobdin (sanek-dobdin)
status: New → Confirmed
Changed in fuel:
milestone: 9.2-mu-5 → 9.2-mu-6
Changed in fuel:
status: Confirmed → Incomplete
Changed in fuel:
milestone: 9.2-mu-6 → 9.x-updates
Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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