Bug 1685724

Summary:	Future dated Sync Plan does not sync first time
Product:	Red Hat Satellite	Reporter:	Stephen Wadeley <swadeley>
Component:	Sync Plans	Assignee:	Samir Jha <sajha>
Status:	CLOSED DUPLICATE	QA Contact:	Stephen Wadeley <swadeley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	egolov, sajha, swadeley
Target Milestone:	Released	Keywords:	PrioBumpQA, TestBlocker, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-15 13:29:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.