Bug 1124923 - Sync Mgmt and Content->Product sync hides CDN errors; needs better messaging/error reporting
Summary: Sync Mgmt and Content->Product sync hides CDN errors; needs better messaging/...
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: sthirugn@redhat.com
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
Reported: 2014-07-30 15:57 UTC by Shannon Hughes
Modified: 2017-02-23 21:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-08-12 05:12:05 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC
Red Hat Bugzilla 1123483 None None None Never
Red Hat Knowledge Base (Solution) 1148833 None None None Never

Internal Links: 1123483

Description Shannon Hughes 2014-07-30 15:57:35 UTC
Description of problem:

Having connection issues with the CDN and see the JSON errors coming back in production foreman log but we are not using the data to inform user there are networking issues with CDN. I had previously cancelled a sync thinking it was hung. when trying to restart the sync the sync goes back to the "cancelled state" within 10 seconds. 

Looking at the production log: 

 Parameters: {"call_report"=>"[FILTERED]", "event_type"=>"repo.sync.finish", "payload"=>{"importer_id"=>"yum_importer", "exception"=>nil, "repo_id"=>"ACME_Corporation-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_RPMs_x86_64_6_5", "traceback"=>nil, "started"=>"2014-07-30T15:46:17-04:00", "_ns"=>"repo_sync_results", "completed"=>"2014-07-30T15:47:20-04:00", "importer_type_id"=>"yum_importer", "error_message"=>nil, "summary"=>{"content"=>{"state"=>"NOT_STARTED"}, "comps"=>{"state"=>"NOT_STARTED"}, "distribution"=>{"state"=>"NOT_STARTED"}, "errata"=>{"state"=>"NOT_STARTED"}, "metadata"=>{"state"=>"FAILED"}}, "added_count"=>0, "result"=>"failed", "updated_count"=>0, "details"=>{"content"=>{"size_total"=>0, "items_left"=>0, "items_total"=>0, "state"=>"NOT_STARTED", "size_left"=>0, "details"=>{"rpm_total"=>0, "rpm_done"=>0, "drpm_total"=>0, "drpm_done"=>0}, "error_details"=>[]}, "comps"=>{"state"=>"NOT_STARTED"}, "distribution"=>{"items_total"=>0, "state"=>"NOT_STARTED", "error_details"=>[], "items_left"=>0}, "errata"=>{"state"=>"NOT_STARTED"}, "metadata"=>{"state"=>"FAILED", "error"=>"HTTPSConnectionPool(host='cdn.redhat.com', port=443): Max retries exceeded with url: /content/dist/rhel/server/6/6.5/x86_64/os/repodata/repomd.xml (Caused by <class 'socket.error'>: [Errno 110] Connection timed out)"}}, "id"=>"53d94bc874702308fca8188c", "removed_count"=>0}, "token"=>"", "api_version"=>"v2", "repository"=>{}}

we can see the HTTPSConnectionPool error with cdn.redhat.com

propose to use the JSON error and craft a message to use to inform there are network/cdn issues.

Comment 1 RHEL Product and Program Management 2014-07-30 16:24:07 UTC
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.

Comment 4 Justin Sherrill 2014-11-04 14:28:42 UTC
So as part of GA, we enhanced the page to show the failure and provide a task to click on, there are additional errors within the task.  Moving to modified.

Comment 6 sthirugn@redhat.com 2015-04-02 04:19:05 UTC
Verified as per Comment 4.  Now task is created for sync.  The progress and the errors can be tracked from there.


Comment 7 sthirugn@redhat.com 2015-04-02 04:53:49 UTC
Although if cdn is not accessible, attempting to enable repositories shows

503 "Service Unavailable"

Comment 8 Bryan Kearney 2015-08-11 13:29:17 UTC
This bug is slated to be released with Satellite 6.1.

Comment 9 errata-xmlrpc 2015-08-12 05:12:05 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.