No longer able to deploy cron.yaml - after 1.3.2

[morten]

Hi,

We have a single cron job in our cron.yaml:

cron:
- description: Daily statistics job
url: /admin/stats?action=runDailyStats
schedule: every day 06:00 # UTC

When we try to deploy this after the 1.3.2 update it fails with:

Error parsing yaml file:
Unable to assign value 'every day 06:00' to attribute 'schedule':
object.__init__() takes no parameters
in "/Users/morten/Development/agon-gae/cron.yaml", line 4, column 13

I don't see anything in the release notes regarding the cron feature,
so I hope somebody can tell us what we need to do to make this cron
job work again.

Best regards,
Morten

[dloomer]

Just adding my +1 to this -- all my deployments are failing. A Google
search for the error message shows this thread as the only result on
the entire Internet, so hopefully someone can help here ;)

[dloomer]

FYI the offending portion of my cron.yaml:

- description: fix gcal
url: /cron/fix_gcal_cron
schedule: every day 00:00
timezone: America/Chicago

[jeffroloff]

I've seen the same problem. It appears that the parsing error aborts
the cron update, so the existing cron jobs are left in place when
viewed from the AppEngine dashboard for my app. Here is the first
entry in my cron.yaml file (the one that causes the failure):

cron:
- url: /email/Sales0/start
schedule: every monday 07:15
timezone: America/Chicago

I really need to change a run time for this weekend, so I'll log this
bug in a few minutes.

Jeff

On Mar 26, 4:12 am, morten <mor...@fusemail.com> wrote:

[jeffroloff]

Just added issue 3020: http://code.google.com/p/googleappengine/issues/detail?id=3020

[jeffroloff]

Looks like a change to /trunk/python/google/appengine/cron/
groctimespecification.py r104 must be the culprit, though I can't see
why. The command line "appcfg.py cron_info" gives the same error
messages as deployment does, and I've found that Interval time specs
(such as "every 30 minutes synchronized") still work, but Specific
time specs (such as "every mon 07:15") don't.

I've noted the above in issue 3020, but I'm discouraged that no
comment came today from anyone on the AppEngine team. cron is not in
experimental mode, so I hope this production code breakage gets some
attention soon!

Jeff

[jeffroloff]

Thanks to a comment from s.podkowinski on the issue tracker, he noted
that use of the 1.3.1 version of the launcher allows a command line
update_cron to succeed. So, I've reverted to the prior version of the
launcher and successfully made the cron changes that I wanted. I
assume that if I'm not using any new 1.3.2 features that I can keep
using the 1.3.1 launcher for development and app deployment - somebody
please let me know if that might cause any problems.

Jeff

[GAEfan]

Same issue here, Monday 3/29/2010

- description: do this cron
url: /do-this-cron
schedule: every day 08:00
timezone: America/Los_Angeles

I will +1 the bug.