Hide Forgot
Description of problem: Syncing of any (new) repository does not work. Log file /var/log/pulp/pulp.log contains message "[Errno 110] Connection timed out", see below for full log. It seems to me that pulp is ignoring http proxy settings (Katello server is without direct connection to Internet). Version-Release number of selected component (if applicable): # rpm -qa '*katello*'|sort katello-1.4.14-1.el6.noarch katello-all-1.4.14-1.el6.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-certs-tools-1.4.4-1.el6.noarch katello-cli-1.4.7-1.el6.noarch katello-cli-common-1.4.7-1.el6.noarch katello-common-1.4.14-1.el6.noarch katello-configure-1.4.9-1.el6.noarch katello-configure-foreman-1.4.9-1.el6.noarch katello-configure-foreman-proxy-1.4.9-1.el6.noarch katello-foreman-all-1.4.14-1.el6.noarch katello-glue-candlepin-1.4.14-1.el6.noarch katello-glue-elasticsearch-1.4.14-1.el6.noarch katello-glue-pulp-1.4.14-1.el6.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-repos-1.4.4-1.el6.noarch katello-selinux-1.4.5-1.el6.noarch pulp-katello-plugins-0.2-1.el6.noarch ruby193-rubygem-foreman-katello-engine-0.0.18-1.el6.noarch ruby193-rubygem-katello_api-0.0.3-2.el6.noarch ruby193-rubygem-katello-foreman-engine-0.0.10-1.el6.noarch signo-katello-0.0.22-1.el6.noarch # uname -a Linux sw 2.6.32-358.28.1.el6.x86_64 #1 SMP Fri Nov 15 11:45:55 EST 2013 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 6.4 (Santiago) Release: 6.4 Codename: Santiago How reproducible: 1) Configure Katello server to use http proxy (no direct connection to Internet) 2) Create new product and repository 3) Sync new repository Steps to Reproduce: 1. # katello-configure --proxy-url=http://myproxy --proxy-port=3128 # katello-configure -c org_name = GPECZ proxy_url = http://myproxy proxy_port = 3128 2. Create new custom product and repository Example: Product Name: Fedora Repository Name: f19-x86_64 Repository URL: http://mirrors.kernel.org/fedora/releases/19/Fedora/x86_64/os/ 3. Go to "Content" -> "Sync Management" -> "Sync Status" Select/Check Repository (f19-x86_64) and "Synchronize Now" Actual results: Error message (after 2 minutes): "There were errors syncing repository 'f19-x86_64'. See notices page for more details." Additional details is empty. Expected results: Downloaded packages in new repository. Additional info: 1) Ineternet access from Katello server through proxy works: # curl -X GET http://mirrors.kernel.org/fedora/releases/19/Fedora/x86_64/os/repodata/repomd.xml --proxy http://myproxy:3128 2) There is no file /etc/pulp/pulp.conf (Katello 1.4) and there is no section with proxy settings in pulp config directory /etc/pulp/: # grep -i proxy -r /etc/pulp/ /var/log/pulp/pulp.log: ======================= 2013-12-01 22:10:39,965 pulp_rpm.plugins.importers.yum.sync:ERROR: sync failed Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pulp_rpm/plugins/importers/yum/sync.py", line 109, in run metadata_files = self.get_metadata() File "/usr/lib/python2.6/site-packages/pulp_rpm/plugins/importers/yum/sync.py", line 194, in get_metadata raise FailedException(str(e)) FailedException: [Errno 110] Connection timed out 2013-12-01 22:10:39,970 pulp.server.event.http:INFO: {'call_report': {'task_group_id': 'eead7a23-b840-4cc4-946a-bf59c8355fac', 'exception': None, 'traceback': None, 'task_id': '60276faa-378d-415a-9983-28e278ac44f4', 'call_request_tags': [u'pulp:repository:GPECZ-Fedora-f19-x86_64', 'pulp:action:sync'], 'reasons': [], 'start_time': '2013-12-01T21:08:33Z', 'tags': [u'pulp:repository:GPECZ-Fedora-f19-x86_64', 'pulp:action:sync'], 'state': 'running', 'finish_time': None, 'dependency_failures': {}, 'schedule_id': None, 'progress': {u'yum_importer': {'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': '[Errno 110] Connection timed out'}}}, 'call_request_group_id': 'eead7a23-b840-4cc4-946a-bf59c8355fac', 'call_request_id': '60276faa-378d-415a-9983-28e278ac44f4', 'principal_login': u'admin', 'response': 'accepted', 'result': None}, 'event_type': 'repo.sync.finish', 'payload': {'importer_id': u'yum_importer', 'exception': None, 'repo_id': u'GPECZ-Fedora-f19-x86_64', 'traceback': None, 'started': '2013-12-01T22:08:33+01:00', '_ns': u'repo_sync_results', 'completed': '2013-12-01T22:10:39+01:00', 'importer_type_id': u'yum_importer', 'error_message': None, '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': '[Errno 110] Connection timed out'}}, 'id': '529ba5cf43b36d068b167f81', 'removed_count': 0}} 2013-12-01 22:10:39,973 pulp.server.dispatch.task:ERROR: Importer indicated a failed response Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pulp/server/dispatch/task.py", line 138, in _run result = call(*args, **kwargs) File "/usr/lib/python2.6/site-packages/pulp/server/managers/repo/sync.py", line 116, in sync raise PulpExecutionException(_('Importer indicated a failed response')) PulpExecutionException: Importer indicated a failed response 2013-12-01 22:10:39,974 pulp.server.dispatch.task:INFO: FAILURE: Task 60276faa-378d-415a-9983-28e278ac44f4: CallRequest: RepoSyncManager.sync(u'GPECZ-Fedora-f19-x86_64', sync_config_override={'num_threads': 4}) 2013-12-01 22:10:40,508 pulp.server.dispatch.call:ERROR: Exception encountered while pickling: call 2013-12-01 22:10:40,509 pulp.server.dispatch.call:ERROR: Can't pickle <function regenerate_applicability_for_repos at 0x7fb05c4a5e60>: it's not found as pulp.server.managers.consumer.applicability.regenerate_applicability_for_repos Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/pulp/server/dispatch/call.py", line 210, in serialize data[field] = pickle.dumps(getattr(self, field)) File "/usr/lib64/python2.6/pickle.py", line 1366, in dumps Pickler(file, protocol).dump(obj) File "/usr/lib64/python2.6/pickle.py", line 224, in dump self.save(obj) File "/usr/lib64/python2.6/pickle.py", line 286, in save f(self, obj) # Call unbound method with explicit self File "/usr/lib64/python2.6/pickle.py", line 748, in save_global (obj, module, name)) PicklingError: Can't pickle <function regenerate_applicability_for_repos at 0x7fb05c4a5e60>: it's not found as pulp.server.managers.consumer.applicability.regenerate_applicability_for_repos 2013-12-01 22:10:40,526 pulp.server.dispatch.task:INFO: SUCCESS: Task 4142060b-354e-49c5-a40c-e0142d9b0f30: CallRequest: regenerate_applicability_for_repos({'sort': None, 'skip': None, 'limit': None, 'filters': {'id': {'$in': ['GPECZ-Fedora-f19-x86_64']}}, 'fields': ['id'], '_id': ObjectId('529ba5d043b36d068b167f87'), 'id': '529ba5d043b36d068b167f87'}) =========================================================
Moving to Sat6 to be tracked there. Upstream bugs are moving to redmine.
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.
6.1 has undergone substantial proxy testing. I do not believe this is an issue any longer.