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 1601951 - Sync Status: Next Sync information is incorrect
Summary: Sync Status: Next Sync information is incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low with 3 votes
Target Milestone: 6.6.0
Assignee: James Jeffers
QA Contact: vijsingh
URL:
Whiteboard:
: 1685590 1693845 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-17 14:16 UTC by John Berninger
Modified: 2019-11-18 18:35 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-katello-3.12.0.rc1-13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:48:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26361 0 Normal Closed Sync Status: Next Sync information is incorrect 2020-03-27 15:31:42 UTC

Description John Berninger 2018-07-17 14:16:13 UTC 
Description of problem:
When viewing Repository in UI, information given in "Sync Status" is self-contradictory. 

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

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Content -> Products -> <Any Product> -> <Any Repository>
2. View Information:

Actual Results:

Sync Status
Sync Interval   Daily at 2017-10-21 06:00:00 UTC (Server Time)
Last Sync       about 7 hours Ago (2018-07-17 07:06:25 UTC Local Time)
Next Sync       Synced manually, no interval set.
Sync State      success

Expected results:
Information in "Next Sync" line matches information in "Sync Interval" line

Additional info:
Comment 2 Brad Buckingham 2019-03-08 19:41:36 UTC 
*** Bug 1685590 has been marked as a duplicate of this bug. ***
Comment 3 Brad Buckingham 2019-03-14 13:46:41 UTC 
Created redmine issue https://projects.theforeman.org/issues/26361 from this bug
Comment 4 Bryan Kearney 2019-03-19 20:01:18 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26361 has been resolved.
Comment 5 Brad Buckingham 2019-04-02 10:17:38 UTC 
*** Bug 1693845 has been marked as a duplicate of this bug. ***
Comment 6 vijsingh 2019-05-21 06:40:00 UTC 
ON_QA Verified

@Satellite 6.6.0 snap 3.0

 1. Navigate to Content -> Products -> <Any Product> -> <Any Repository>
 2. View Information:

 
Observation:
 
'Information in "Next Sync" line matches information in "Sync Interval" line'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sync Status

Sync Interval Synced manually, no interval set.               <<===
Last Sync 22 hours ago (May 20, 8:06 AM Local Time)
Next Sync Synced manually, no interval set.                   <<===
Sync State success
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comment 8 Bryan Kearney 2019-10-22 19:48:06 UTC 
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:3172
Note You need to log in before you can comment on or make changes to this bug.