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

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 1902077 - [RFE] Ability to See if Individual Repositories on Capsule Server Synced Successfully from Satellite UI
Summary: [RFE] Ability to See if Individual Repositories on Capsule Server Synced Succ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.8.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: 2020-11-26 19:07 UTC by myoder
Modified: 2024-06-06 00:36 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description myoder 2020-11-26 19:07:12 UTC
Description of problem:

With an environment having many Capsules, it is not always easy to tell if Capsules are synced properly.  Many times the issue is not noticed until systems try to update, or users try to provision systems relying on synced Capsule content to provision.  Fixing the Capsule syncs is not always a simple task, and can take troubleshooting the issue days to weeks.

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


Actual results:
There is a Content tab showing all the content-views and lifecycle environments synced for each Capsule when navigating to Infrastructure => Capsules, and selecting a Capsule server.  This page also displays counts for repos, packages, etc.  However, there is no detail about individual repositories, and if they synced successfully or not.

Expected results:
Ability to see granularly all repositories that synced successfully on Capsule server, and which repositories have issues.  Would be very convenient to have an interface similar to the synced repositories page found under Content => Sync Status, for each Content section of the Capsule server.  The dynflowd subtasks from a Capsule sync will show us warnings/errors for individual repositories that fail (however this is a pain to dig into, and is not easily kept track of).  Perhaps we could keep track of all successful and warnings/error syncs for repositories on Capsules, and display it on the Content tab for each Capsule.  Either link to the failed subtasks, or have a UI similar to our repositories page found at Content => Sync Status, where users can see all repositories on the Capsule, and if the last sync was successful or not.

Additional info:

Comment 3 Brad Buckingham 2022-12-02 18:42:02 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2023-01-04 18:41:55 UTC
Based upon initial feedback during auto-close, this bugzilla will remain open for the time being.

Comment 9 Eric Helms 2024-06-06 00:36:27 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.