Project

General

Profile

Bug #16035

Incorrect Next Sync date calculation in weekly Sync Plan

Added by Walden Raines over 2 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1302098
Description of problem:

Setting the Start Date for some weekly Sync Plan schedules results in an incorrect date calculation that causes the Next Sync date to skip a week.

Issue appears to be linked at at one specific date.

Version-Release number of selected component (if applicable):

Satellite 6.1.5 at least

How reproducible: Appears to be every time

Steps to Reproduce:
1. Create weekly Sync Plan
2. Set Start Date to Jan 22, 2016 (may be date specific)
3. Next Sync date should show Feb 5, 2016 (skipping Jan 29, 2016)

Actual results:

Next Sync date reports Feb 5, 2016

Expected results:

Next Sync should be Jan 29, 2016

Additional info:

Customer reported this in their environment and it was also reproduced in house with the start date Jan 22, 2016. Using the start date Jan 25, 2016 /did not/ reproduce the error.

Associated revisions

Revision 08e85148 (diff)
Added by Walden Raines over 2 years ago

Fixes #16035: fix next sync calculation for weekly sync plans.

The weekly sync plan calculation was adding an extra 7 days in all cases
where it should have only been adding 7 days if the day of the week was
before the current day.

http://projects.theforeman.org/issues/16035

Revision 05c563d0
Added by Walden Raines over 2 years ago

Merge pull request #6238 from waldenraines/16035

Fixes #16035: fix next sync calculation for weekly sync plans.

History

#1 Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6238 added

#2 Updated by Walden Raines over 2 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Justin Sherrill over 2 years ago

  • Legacy Backlogs Release (now unused) set to 162

Also available in: Atom PDF