Job scheduling issue with rundeck 1.5

[ksa1983]

Job scheduling seems to be broken in rundeck 1.5 if send notification is enabled.
For any job with send notification set to yes and scheduled to run repeatedly on any future date, initially works fine as shown below.
for Example :- Job scheduled on

at 22 : 00 on day 25 of May of year 2013
Next execution in 1d at Sat May 25 22:00:00 EDT 2013

Ths job is set to run in 1d

If we edit the job again and schedule the job to some back date it still says the job will execute in 1d.

at 22 : 00 on day 25 of May of year 2012
Next execution in 1d at Sat May 25 22:00:00 EDT 2013

Even though the date is moved to 2012 it will let you save the job and also executes the job.

Please let me know if more information needed.

https://groups.google.com/forum/?fromgroups#!topic/rundeck-discuss/-dYWkY8xn7Y

[ksa1983]

Hi Greg,

I tried to replicate this issue in newer release version 1.6 and it is still there. Is there a temporary fix for this issue?

Thanks

[gschueler]

Hi i have not had a chance to look into this bug, but I will schedule it for 1.6.1 to take a look asap

[ksa1983]

Thanks!

[gschueler]

crontab appears to not be validated if notification is set