Description of problem: There are times when syncing RHEL repositories via Katello fail without a clear explanation. After DEV performed some investigation, it looks like there is a valid reason for the failure but pulp only exposes a generic failure message tucked in a traceback attribute with the message: PulpExecutionException: Importer indicated a failed response Eventually this pulp task gets moved to a 'history' queue where finally it gets the actual error failure added to its 'summary' attribute: {"error"=>"Cannot retrieve repository metadata (repomd.xml) for repository: ACME_Corporation-FailProduct-FailRepo. Please verify its path and try again"} Also, see https://bugzilla.redhat.com/show_bug.cgi?id=965218 for some needed pulp work. Version-Release number of selected component (if applicable): * python-pulp-client-lib-2.1.1-0.10.beta.el6.noarch * python-pulp-bindings-2.1.1-0.10.beta.el6.noarch * pulp-selinux-2.1.1-0.10.beta.el6.noarch * pulp-server-2.1.1-0.10.beta.el6.noarch * pulp-admin-client-2.1.1-0.10.beta.el6.noarch * pulp-rpm-plugins-2.1.1-0.10.beta.el6.noarch * pulp-builtins-admin-extensions-2.1.1-0.10.beta.el6.noarch * python-pulp-rpm-common-2.1.1-0.10.beta.el6.noarch * katello-glue-pulp-1.4.2-1.git.411.375f44b.el6.noarch * python-pulp-common-2.1.1-0.10.beta.el6.noarch How reproducible: Steps to Reproduce: 1. I was able to trigger it by syncing Red Hat Enterprise Linux 6 Server x86_64 (RPMs) and Red Hat Enterprise Linux 6 Server x86_64 - Optional (RPMs) 2. 3. Actual results: Sync fails but there's no UI explanation as to why it failed. Expected results: Additional info:
The fix is being tracked here - https://github.com/Katello/katello/pull/2939
Fixed in 7c914a89453e8020bb941cb9f2b63c3e4a503150 If an error occurs while syncing, the user will get an immediate display of 'Erro Syncing' and a tooltip will appear next to that entry in the table. This tooltip will contain the list of errors encountered while syncing. This display of error status and reasoning will also persist through page refreshes until the repository syncs correctly at a later date.
Though there is a tooltip now displayed in the table, the tooltip is empty (see attached screenshot) until you reload the page. Also, the notification does not show up until you navigate away from the Sync page. Once you go back to the sync page, the tooltip will show a message (in my case, "Not found"). * Create a YUM repo and point it to http://www.yahoo.com * Sync it Environment: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.8.25-1.el6sam.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.8.25-1.el6sam.noarch * candlepin-tomcat6-0.8.25-1.el6sam.noarch * elasticsearch-0.19.9-8.el6sat.noarch * foreman-1.3.0-18.el6sat.noarch * foreman-compute-1.3.0-18.el6sat.noarch * foreman-libvirt-1.3.0-18.el6sat.noarch * foreman-postgresql-1.3.0-18.el6sat.noarch * foreman-proxy-1.3.0-3.el6sat.noarch * katello-1.4.6-39.el6sat.noarch * katello-all-1.4.6-39.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.4-1.el6sat.noarch * katello-cli-1.4.3-24.el6sat.noarch * katello-cli-common-1.4.3-24.el6sat.noarch * katello-common-1.4.6-39.el6sat.noarch * katello-configure-1.4.7-5.el6sat.noarch * katello-configure-foreman-1.4.7-5.el6sat.noarch * katello-configure-foreman-proxy-1.4.7-5.el6sat.noarch * katello-foreman-all-1.4.6-39.el6sat.noarch * katello-glue-candlepin-1.4.6-39.el6sat.noarch * katello-glue-elasticsearch-1.4.6-39.el6sat.noarch * katello-glue-pulp-1.4.6-39.el6sat.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.4.4-4.el6sat.noarch * openldap-2.4.23-31.el6.x86_64 * pulp-katello-plugins-0.2-1.el6sat.noarch * pulp-nodes-common-2.3.0-0.22.beta.el6sat.noarch * pulp-nodes-parent-2.3.0-0.22.beta.el6sat.noarch * pulp-puppet-plugins-2.3.0-0.22.beta.el6sat.noarch * pulp-rpm-plugins-2.3.0-0.22.beta.el6sat.noarch * pulp-selinux-2.3.0-0.22.beta.el6sat.noarch * pulp-server-2.3.0-0.22.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.0.7-1.el6sat.noarch * signo-0.0.22-2.el6sat.noarch * signo-katello-0.0.22-2.el6sat.noarch
Created redmine issue http://projects.theforeman.org/issues/5986 from this bug
Created attachment 922188 [details] Tooltip properly shows information
Verified: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.19-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.19-1.el6_5.noarch * candlepin-tomcat6-0.9.19-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.6.0.32-1.el6sat.noarch * foreman-compute-1.6.0.32-1.el6sat.noarch * foreman-gce-1.6.0.32-1.el6sat.noarch * foreman-libvirt-1.6.0.32-1.el6sat.noarch * foreman-ovirt-1.6.0.32-1.el6sat.noarch * foreman-postgresql-1.6.0.32-1.el6sat.noarch * foreman-proxy-1.6.0.22-1.el6sat.noarch * foreman-selinux-1.6.0.3-1.el6sat.noarch * foreman-vmware-1.6.0.32-1.el6sat.noarch * katello-1.5.0-27.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-installer-0.0.56-1.el6sat.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-0.3-3.el6sat.noarch * pulp-nodes-common-2.4.0-0.23.beta.el6sat.noarch * pulp-nodes-parent-2.4.0-0.23.beta.el6sat.noarch * pulp-puppet-plugins-2.4.0-0.23.beta.el6sat.noarch * pulp-puppet-tools-2.4.0-0.23.beta.el6sat.noarch * pulp-rpm-plugins-2.4.0-0.23.beta.el6sat.noarch * pulp-selinux-2.4.0-0.23.beta.el6sat.noarch * pulp-server-2.4.0-0.23.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch * rubygem-hammer_cli-0.1.1-10.el6sat.noarch * rubygem-hammer_cli_foreman-0.1.1-13.el6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch * rubygem-hammer_cli_katello-0.0.4-9.el6sat.noarch
This was delivered with Satellite 6.0 which was released on 10 September 2014.
customer hit this with rhel 7 rh common repos. sycn shows 99 packages but gets a trace back in /var/log/messages and webui shows incomplete. After a reindex showing the packages in the webui though so it looks like the sync completed.
Did the customer hit an issue with syncing or an issue with an error not being displayed to them after hitting an error syncing?
The customer synced the repo and did not get an error after hitting the sync button. Since its in a incomplete state its not letting us add it to a content view or use the repo. - Chris
We have similar issues, even with latest updates.
Created attachment 997541 [details] Error indicating Forbidden
Created attachment 997542 [details] Importer indicated a failed response
Created attachment 997558 [details] Sync complete - but failed Sometimes the result displays "Sync complete" but not all packages have been downloaded: "New packages: 307 (173 MB). Failed to download 6 packages." Raw task log lists failed packages (but "Error" tab says no error): {"yum_importer"=> {"content"=> {"size_total"=>181200544, "items_left"=>0, "items_total"=>307, "state"=>"FINISHED", "size_left"=>0, "details"=> {"rpm_total"=>307, "rpm_done"=>307, "drpm_total"=>0, "drpm_done"=>0}, "error_details"=> [{"url"=> "https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/Packages/nodejs010-nodejs-ansicolors-0.3.2-1.el7.noarch.rpm", "response_code"=>403, "response_msg"=>"Forbidden"}, {"url"=> "https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/Packages/php55-php-odbc-5.5.6-13.el7.x86_64.rpm", "response_code"=>403, "response_msg"=>"Forbidden"}, .... Subsequent attempts download more and more packages, sometimes. It is not reproducable when access to the XML is forbidden, when access to some RPMs is forbidden, and when everything runs fine.
Reading through the comments, the UI appears to be displaying the proper status and information to the user which is what this bug was originally intended to address. If a few packages are unable to be downloaded the repository is not considered to be in an error state since this can occur to do Forbidden's, missing RPMs or network issues. The task details display the specifics per package. Does this address your issue? What else would you like to see specific to this bug?