Description of problem: I have tried to use various examples of Quarts cron format and was not able to specify year. http://www.quartz-scheduler.org/docs/tutorials/crontrigger.html Version-Release number of selected component (if applicable): Galactica 20100910.2 quartz-1.8.1-3.el5sat spacewalk-taskomatic-1.2.35-1.el5sat How reproducible: 1 of 1 satellite Steps to Reproduce: 1. Create repos and channel, assign some repo(s) to the channel 2. Go to Channels -> Manage Software Channels -> <channel> -> Repositories -> Sync -> Custom Cron format: 3. Enter "0 15 10 ? * * 2011" (~ every day in 10:15 in year 2011) and click on "Schedule" Actual results: Red warning saying: "Invalid schedule entry: 0 15 10 ? * * 2011" Expected results: Should work or there should be a link to supported formats of input
This would be nice to have fixed. I don't see us blocking release for it. I assume this is mostly functional, but some syntax is not available. We may want to do kbase initially for customers on accepted input. Cliff
Another not accepted input from Quarz examples: 0 15 10 ? * 6#3 Fire at 10:15am on the third Friday of every month 0 0 12 1/5 * ? Fire at 12pm (noon) every 5 days every month, starting on the first day of the month. 0 11 11 11 11 ? Fire every November 11th at 11:11am.
I believe my fixes for 634834 already fixed this, as I am not able to reproduce with my current devel setup or with spacewalk-java-1.2.39-9.el5sat which was built on the 21st.
All of the stated cron expressions are now accepted: 0 15 10 ? * * 2011 0 15 10 ? * 6#3 0 0 12 1/5 * ? 0 11 11 11 11 ? I tested following cron expressions (similar to those reported in the BZ) and verified the repository got synced: 0 48 05 ? * * 2010 5:48 every day during 2010 0 08 6 ? * 4#1 06:08 every 1st Thr every month 0 15 6 1/5 * ? 06:15 every 5 days every month starting on the 1st day of the month 0 17 6 6 10 ? 06:17 on 6th of Oct every year VERIFIED with spacewalk-java-1.2.39-26.el5sat on Satellite-5.4.0-RHEL5-re20101001.1
Verified in stage. Expressions from comment #5 work.
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332 RHEA-2010:0803 - RHN Tools enhancement update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333 RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334 RHEA-2010:0800 - RHN Satellite Server 5.4.0 https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335 Docs are available: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html Regards, Clifford