Bug 1956985

Summary:	[RFE] Capsule Last Sync date and status should not be based on task data.
Product:	Red Hat Satellite	Reporter:	rakesh kumar <rakumar>
Component:	Sync Plans	Assignee:	Samir Jha <sajha>
Status:	CLOSED ERRATA	QA Contact:	Sam Bible <sbible>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, jsherril, pcreech
Target Milestone:	6.13.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rubygem-katello-4.7.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:20:33 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 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