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.
Bug 1685724 - Future dated Sync Plan does not sync first time
Summary: Future dated Sync Plan does not sync first time
Keywords:
Status: CLOSED DUPLICATE of bug 1655595
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Released
Assignee: Samir Jha
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 22:07 UTC by Stephen Wadeley
Modified: 2019-10-07 17:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-15 13:29:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25655 0 Normal Closed Sync plans does not start 'repositories sync' first time as per defined "Start Date" and same happened for all 'hourly/d... 2020-10-15 08:32:31 UTC

Description Stephen Wadeley 2019-03-05 22:07:02 UTC 
Description of problem:

Daily sync plan for a custom product;s repo was not synced 


Version-Release number of selected component (if applicable):
~]# rpm -q foreman
foreman-1.20.1.10-1.el7sat.noarch
~]# rpm -q tfm-rubygem-katello
tfm-rubygem-katello-3.10.0.24-1.el7sat.noarch


How reproducible:

Repeated fails when running:

tests/foreman/cli/test_syncplan.py::SyncPlanTestCase::test_positive_synchronize_custom_products_future_sync_date 


Steps to Reproduce:
1. Create a Daily sync plan with sync date and time in an hours time
2. make products
3. make repos yum for the products
4. Associate sync plan with products
5. Update sync time to be just a few minutes time

Actual results:

Repo is not synced at expected time


Expected results:

Repo is synced at expected time


Additional info:

[Bug 1685590] Next Sync time is not set on Products Repos details page
Comment 15 Bryan Kearney 2019-03-14 14:00:57 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25655 has been resolved.
Note You need to log in before you can comment on or make changes to this bug.