Bug #15797
Updated by Justin Sherrill over 7 years ago
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1294196 1. Proposed title of this feature request >> [RFE]User friendly error message on GUI/hammer while falling to sync gitlab/third-part repository on the Satellite. 2. Who is the customer behind the request? >> Account: name -Alexander Waldekker Account Number-659379 TAM customer: No SRM customer: No Strategic: No 3. What is the nature and description of the request? >> we should have user friendly error message while falling to sync gitlab/third-party repository on the Satellite as it fail silently without any error message. 4. Why does the customer need this? >> For better customer experience. 5. How would the customer like to achieve this? (List the functional requirements here) >> By reflecting the error message on GUI when gitlab/third-party repository fail to sync. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. >> Create a product and custom repository in satellite gui/hammer with following link to a repo: https://packages.gitlab.com/gitlab/gitlab-ce/el/7/x86_64 and then try to sync that repository and check if we can see any error message. Note: Satellite requires repo metadata, specifically <checksum>-filelists.xml file to sync repo and gitlab repository doesn't provide a valid filelists.xml database therefore we won't able to sync gitlab repository on the Satellite. Please refer below Bugzilla for more information: ~~ https://bugzilla.redhat.com/show_bug.cgi?id=1267579 ~~ 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? >> No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? >> Customer would like to have this feature implemented in the satellite v 6 as soon as possible. Can we consider this for Satellite v 6.2 release? 9. Is the sales team involved in this request and do they have any additional input? >> No 10. List any affected packages or components. >> NA 11. Would the customer be able to assist in testing this functionality if implemented? >> Yes