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)
Next Sync date reports Feb 5, 2016
Next Sync should be Jan 29, 2016
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.
I heard from the on site DEE that while the Next Sync date displayed Feb 5, the since actually execute and run on Jan 29 as would normally be expected.
In other words, the logic seems to work (e.g., every Friday), just the display of the next date the sync will run was in error (e.g., the following Friday).
Created redmine issue http://projects.theforeman.org/issues/16035 from this bug
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/16035 has been closed
Thanks for the update Bryan. Would we expect to see this in 6.2.2 or will we need to wait for 6.3 since it landed in the current foreman?
Verified in Sat 6 snap 5. Next sync is calculated correctly for weekly sync in case the start date is less than a week in past from the current day.
Verified in 6.2.5
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.