Bug #1811

If more than one scheduled actions fit in a scheduler cycle, the behaviour is unexpected

Added by Carlos Martín over 8 years ago. Updated about 7 years ago.

Status:NewStart date:03/13/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Scheduler
Target version:-
Resolution: Pull request:
Affected Versions:OpenNebula 4.0

Description

Scheduled actions are processed in order. If the scheduler does its thing at 10:00 and 10:15, these two VMs will have different results:

SCHEDULED ACTIONS                                                               
ID ACTION          SCHEDULED         DONE MESSAGE
 0 snapshot-create 09/20 10:05            -      
 1 cancel          09/20 10:10            -      

SCHEDULED ACTIONS                                                               
ID ACTION          SCHEDULED         DONE MESSAGE
 0 cancel          09/20 10:10            -      
 1 snapshot-create 09/20 10:05            -

We should sort the actions by time. And maybe just execute the first one.

Related issues

Related to Feature #1483: Define VM deploy and shutdown times for the scheduler Closed 09/20/2012

History

#1 Updated by Ruben S. Montero about 8 years ago

  • Priority changed from Normal to Low

#2 Updated by Ruben S. Montero almost 8 years ago

  • Target version set to Release 4.4

#3 Updated by Ruben S. Montero over 7 years ago

  • Target version changed from Release 4.4 to Release 4.6

#4 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from Low to Normal

#5 Updated by Jaime Melis over 7 years ago

  • Target version changed from Release 4.6 to Release 4.8

#6 Updated by Ruben S. Montero about 7 years ago

  • Target version deleted (Release 4.8)

Also available in: Atom PDF