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 2159629 - Sync status of a Sync Plan or Product is confusing
Summary: Sync status of a Sync Plan or Product is confusing
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.11.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-10 08:26 UTC by Pavel Moravec
Modified: 2024-06-06 16:04 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:04:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19609 0 None Migrated None 2024-06-06 16:04:44 UTC
Red Hat Knowledge Base (Solution) 7028173 0 None None None 2023-08-16 15:51:00 UTC

Description Pavel Moravec 2023-01-10 08:26:16 UTC
Description of problem:
Querying for a Sync status of a Sync Plan or a Product via API endpoints:

GET /katello/api/sync_plans/:id
GET /katello/api/v2/products?organization_id=:id&sync_plan_id=:id
(possibly others)

return sync status of the very last *repository* within the Sync Plan or Product. That is sometimes confusing, when you:

- sync 5 repos of a product, 4 of them fail
- now, the sync status shows "Incomplete sync"
  - as the latest sync relevant to the product was bulk task of syncing 5 repos, that (partially) failed
- syncing one of failed repos succeeds
- now, the sync status shows "Syncing Complete." for the whole product / sync plan
  - as the latest sync relevant to the product was a single repo sync that succeeded - ignoring the other repos failed during their latest sync


This logic "take an outcome of latest product-relevant sync, regardless of the sync scope" should be be either documented (in APIdoc also), or improved to query each and every repo of the product.


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


How reproducible:
100%


Steps to Reproduce:
1. Have a custom product with 2 repos, one with valid feed URL, second with invalid URL
2. Create a Sync Plan for the Product
2. Sync *Product* and check sync status of the Sync Plan / Product 
3. Sync just the correct repo


Actual results:
2. Shows "Incomplete sync." (which is correct)
3. Shows "Syncing Complete.", despite nothing really changed from point 2.


Expected results:
3. to show "Incomplete sync"  OR  document this behaviour as described above


Additional info:

Comment 1 Eric Helms 2024-06-06 16:04:45 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.