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 1956985 - [RFE] Capsule Last Sync date and status should not be based on task data.
Summary: [RFE] Capsule Last Sync date and status should not be based on task data.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.9.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.13.0
Assignee: Samir Jha
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 19:39 UTC by rakesh kumar
Modified: 2024-06-14 01:26 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-4.7.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:20:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35407 0 High Closed Capsule Last Sync date and status should not be based on task data. 2022-09-02 18:44:56 UTC
Red Hat Issue Tracker SAT-15866 0 None None None 2023-05-11 07:31:00 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:20:50 UTC

Description rakesh kumar 2021-05-04 19:39:29 UTC 
Description of problem:
Last sync status and date come from tasks, if we clear sync tasks from Satellite then that data is not available to show on the UI hence Satellite shows repo is never synced. And the same issue with the capsule sync as well.


We should add a new table(or a column in some existing table) in the database where we can keep the record of repo/capsule sync and fetch the date/status from there to show on UI.

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

Satellite 6.9
Comment 5 Samir Jha 2022-08-22 14:08:30 UTC 
Created redmine issue https://projects.theforeman.org/issues/35407 from this bug
Comment 6 Bryan Kearney 2022-08-23 16:03:39 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35407 has been resolved.
Comment 9 Sam Bible 2023-01-30 20:30:06 UTC 
Verified on Satellite 6.13 - Snap 8

Steps to Verify:
1) Synchronize a repository.
2) Synchronize a capsule.
3) Grab the task id for both of these operations.
4) Using foreman-rake, run this command `::ForemanTasks::Task.find('<task_id>').delete
5) Check the sync status of both the repository, and the capsule

Expected Results:
The sync status should still show as synchronized, with the right date and time

Actual Results:
Both objects still show the proper Sync status

Additional Info:
The usage of foreman-rake here as a way to trigger the behavior is out of necessity, and the originally observed customer behavior involves an automated cleanup
of old tasks, which would be difficulty to reproduce. The outcome is the same though.
Comment 13 errata-xmlrpc 2023-05-03 13:20:33 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 (Important: Satellite 6.13 Release), 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-2023:2097
Note You need to log in before you can comment on or make changes to this bug.