Actions
Bug #34741
closed
CronParser misbehaves if the cronline and reference time are in different timezones
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
pry(main)> tz=ActiveSupport::TimeZone['America/New_York']
=> #<ActiveSupport::TimeZone:0x000000000ea1eec0 @name="America/New_York", @tzinfo=#<TZInfo::DataTimezone: America/New_York>, @utc_offset=nil>
pry(main)> now = tz.now
=> Wed, 06 Apr 2022 04:15:14 EDT -04:00
pry(main)> CronParser.new('6 6 6 * *', tz).next(now)
=> Wed, 06 Apr 2022 06:06:00 EDT -04:00
pry(main)> CronParser.new('6 6 6 * *', tz).next(now.utc)
=> Fri, 06 May 2022 06:06:00 EDT -04:00
Updated by The Foreman Bot over 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/680 added
Updated by The Foreman Bot over 3 years ago
- Fixed in Releases foreman-tasks-6.0.2 added
Updated by Adam Ruzicka over 3 years ago
- Related to Bug #34691: Repeated Ansible run scheduling adds extra time to specified start date added
Updated by Adam Ruzicka over 3 years ago
- Status changed from Ready For Testing to Closed
- Triaged changed from No to Yes
- Bugzilla link set to 2052048
- Fixed in Releases foreman-tasks-5.2.3 added
Actions