Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
The tasks list provides a good overview what is being processed in the background. Also repo syncs are included. But it is unclear what triggered the repo sync. If it was e.g. started from a Sync plan or manual.
It would be good to have an entry in the tasks lists that a Sync plan is being started and finished.


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


How reproducible:


Steps to Reproduce:
1. Create a hourly sync plan to sync a product
2.
3.

Actual results:
Only tasks that repos are sync, there is no reference included that it was started from a scheduled sync plan

Expected results:
Reference included that a sync plan is started&finsihed and which tasks below to the sync plan

Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Per 6.3 planning, moving out non acked bugs to the backlog

This is available in 6.2 where there is a parent task and sub tasks.