Description of problem: The database field for Quartz schedule is only 20 chars wide. Any trivial schedule can easily overflow this limit. Version-Release number of selected component (if applicable): 2.0 How reproducible: every time Steps to Reproduce: 1. set quartz schedule to anything over 20 char (eg. '* * 12,18 ? MON-FRI *') Actual results: INFO | jvm 3 | 2014/02/26 20:16:25 | 2014-02-26 20:16:25,129 [Thread-13] ERROR org.hibernate.util.JDBCExceptionReporter - ERROR : value too long for type character varying(20) ... INFO | jvm 3 | 2014/02/26 20:16:25 | Caused by: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(20) ... INFO | jvm 3 | 2014/02/26 20:16:25 | WARNING: org.hibernate.exception.DataException: could not insert: [com.redhat.rhn.taskomatic.TaskoSchedule] Expected results: successful record insertion Additional info:
Taking ...
extending the cron_expr column to 50 ... spacewalk.git: facabbe66d5e811913fef328dcdde00df08c9623
Not to be pedantic but... 0 5,18,42,50 3,5,9,12,15,20,22 ? MON,TUES,FRI,SAT JAN,FEB,MAY,JUN,SEP,DEC * Is WAY more than 50 chars too. I'd say 100 chars is more like it.
I also should mention that the WebUI needs to be adjusted too.
All right, extending the cron_expr column to 120, however I doubt anybody would use it ... spacewalk.git: bb84025adea49359eac62e1ddb3277ba20aeb0c3 Note that the cron expression for Comment#3 isn't valid.
Spacewalk 2.2 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22