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:

Sync plans does not start 'repositories sync' first time as per defined "Start Date" and same happened for all 'hourly/daily/weekly' intervals

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

Satellite 6.5.0 snap 6

How reproducible:
Always

Steps to Reproduce:

1. Go to Satellite GUI: 
    
    Content => Sync Plans => Create Sync Plan => set internal 'hourly/daily/weekly' => Submit

   Click on same sync plan => Products => select and add product

2. Keep check the product repository sync as per first sync("Start Date")


Actual results:

 No sync task will create as per defined "Start Date" .

Expected results:

 Added product repositories should start syncing as per "Start Date".

Additional info:

Created redmine issue http://projects.theforeman.org/issues/25655 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25655 has been resolved.

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25655 has been resolved.

*** Bug 1685724 has been marked as a duplicate of this bug. ***

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/RHSA-2019:1222