[Bug 1819369] [NEW] When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*
Markus Ueberall
ueberall at projektzentrisch.de
Sun Mar 10 19:45:14 UTC 2019
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description: Ubuntu 16.04.6 LTS
Release: 16.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
# apt-cache policy cron
cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
*** 3.0pl1-128ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
/etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync):
# m h dom mon dow user command
00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1
00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2
00 05 15-21 1,3,5,7,9,11 SAT sys-maint some-task some-option #host3
00 05 22-28 1,3,5,7,9,11 SAT sys-maint some-task some-option #host4
The expectation was that none of the entries is executed in parallel at
any given point in time due to column three (date of month range).
(Note: All other (default) entries work as expected, syntax of all
crontab files has been checked using
https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
4) What happened instead
Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts.
** Affects: cron (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description: Ubuntu 16.04.6 LTS
Release: 16.04
-
2) The version of the package you are using, via 'apt-cache policy pkgname'
# apt-cache policy cron
cron:
- Installed: 3.0pl1-128ubuntu2
- Candidate: 3.0pl1-128ubuntu2
- Version table:
- *** 3.0pl1-128ubuntu2 500
- 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
-
+ Installed: 3.0pl1-128ubuntu2
+ Candidate: 3.0pl1-128ubuntu2
+ Version table:
+ *** 3.0pl1-128ubuntu2 500
+ 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
3) What you expected to happen
/etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync):
# m h dom mon dow user command
00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1
00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2
00 05 15-21 1,3,5,7,9,11 SAT sys-maint some-task some-option #host3
00 05 22-28 1,3,5,7,9,11 SAT sys-maint some-task some-option #host4
The expectation was that none of the entries is executed in parallel at
any given point in time due to column three (date of month range).
(Note: All other (default) entries work as expected, syntax of all
- crontab files have been checked using
+ crontab files has been checked using
https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
-
4) What happened instead
Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts.
** Summary changed:
- When specifying specific minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored*
+ When specifying minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored*
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1819369
Title:
When specifying minute,hour,day-of-month,month,day-of-week
values/ranges, given day-of-month range is *ignored*
Status in cron package in Ubuntu:
New
Bug description:
1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description: Ubuntu 16.04.6 LTS
Release: 16.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
# apt-cache policy cron
cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
*** 3.0pl1-128ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
/etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync):
# m h dom mon dow user command
00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1
00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2
00 05 15-21 1,3,5,7,9,11 SAT sys-maint some-task some-option #host3
00 05 22-28 1,3,5,7,9,11 SAT sys-maint some-task some-option #host4
The expectation was that none of the entries is executed in parallel
at any given point in time due to column three (date of month range).
(Note: All other (default) entries work as expected, syntax of all
crontab files has been checked using
https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
4) What happened instead
Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1819369/+subscriptions
More information about the foundations-bugs
mailing list