This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2256010 - Last synced time is wrong or misleading.
Summary: Last synced time is wrong or misleading.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-27 17:54 UTC by mithun kalyat
Modified: 2024-06-06 16:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:39:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31318 0 Normal New Red Hat products that were never synced are reporting last synced time 2024-01-08 22:35:37 UTC
Red Hat Issue Tracker   SAT-22156 0 None Migrated None 2024-06-06 16:39:53 UTC

Description mithun kalyat 2023-12-27 17:54:59 UTC 
Description of problem:

Last synced time is wrong or misleading.

How reproducible:

The 'Sync status' under products is misleading. It shows the 'Last synced' time as time ago, but the repository was never synced, instead just enabled.

Steps to Reproduce:

1. Enable the repositories but do not sync it. 

2. Check the 'Sync status'.

    Content --> Products


Actual results:

The 'Sync status' should be showing the actual output of a sync result. If it meant just that the repository is in sync with the manifest, the message needs to be modified accordingly.


Additional info:

Attaching the screenshots for the reference.
Comment 4 Ian Ballou 2024-01-08 22:35:37 UTC 
This issue is not a regression and I think has been around for as long as the Products page has existed. There is a made-up sync time for products that have never had a repository synced.

I found an older redmine, linking it up.

I would set this as a low priority since it's been around for so long and since it goes away once you sync something in the product.
Comment 6 Eric Helms 2024-05-16 16:18:06 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31318 has been resolved.
Comment 7 Eric Helms 2024-06-06 16:39:54 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.