Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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).
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.
https://access.redhat.com/errata/RHBA-2016:2940