Issue #2006
closediso importer fails without useful error message
Description
A sync with the iso/file importer results in a failure but no error message. Data below is from a bugzilla report:
I created a new product, with a new file based repository. I pointed it at
https://www.redhat.com/security/data/oval
which has a PULP_MANIFEST. Some of the line seem to have the wrong size:
Red_Hat_Enterprise_Linux_3.xml,742e60b5c523bb3d338aab83ad0ecfe4b5975a22878fa1b5ade8bcf7c0d1af94,25
Red_Hat_Enterprise_Linux_4.xml,e8c5250c1cf2c205adc37be24701e34d80770dc33f69cb9ef38c6f165dec07ff,25
Red_Hat_Enterprise_Linux_5.xml,b4d4bd7d2e885ad2a687c5472cc19c7b4c9b106b70053f7b8dde3ccc439105e1,25
Red_Hat_Enterprise_Linux_6.xml,4b18a4387bde59901286277a464f07427339cfb8382c9360249bf0e809f0cb24,25
Red_Hat_Enterprise_Linux_7.xml,62581bdcde36e8cd0922c7f8d71ccf02722209b8913b283f006d713dbe214e39,25
{"pulp_tasks"=>
[{"exception"=>nil,
"task_type"=>"pulp.server.managers.repo.sync.sync",
"_href"=>"/pulp/api/v2/tasks/16ce2fc9-a214-422b-a902-b02ccd47bc52/",
"task_id"=>"16ce2fc9-a214-422b-a902-b02ccd47bc52",
"tags"=>
["pulp:repository:Default_Organization-OVAL_Data-Red_Hat_Security",
"pulp:action:sync"],
"finish_time"=>"2016-04-27T16:06:40Z",
"_ns"=>"task_status",
"start_time"=>"2016-04-27T16:03:21Z",
"traceback"=>
"Traceback (most recent call last):\n File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240, in trace_task\n R = retval = fun(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 473, in __call__\n return super(Task, self).__call__(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 103, in __call__\n return super(PulpTask, self).__call__(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 437, in __protected_call__\n return self.run(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py\", line 810, in sync\n raise pulp_exceptions.PulpExecutionException(_('Importer indicated a failed response'))\nPulpExecutionException: Importer indicated a failed response\n",
"spawned_tasks"=>[],
"progress_report"=>
{"iso_importer"=>
{"error_message"=>nil,
"traceback"=>nil,
"finished_bytes"=>197828744,
"num_isos"=>2927,
"state"=>"isos_failed",
"total_bytes"=>153780117,
"state_times"=>
{"not_started"=>"2016-04-27T16:03:21",
"manifest_in_progress"=>"2016-04-27T16:03:21",
"isos_failed"=>"2016-04-27T16:06:39",
"isos_in_progress"=>"2016-04-27T16:03:30"},
"num_isos_finished"=>2922,
"iso_error_messages"=>
[{"name"=>"Red_Hat_Enterprise_Linux_5.xml", "error"=>{}},
{"name"=>"Red_Hat_Enterprise_Linux_4.xml", "error"=>{}},
{"name"=>"Red_Hat_Enterprise_Linux_6.xml", "error"=>{}},
{"name"=>"Red_Hat_Enterprise_Linux_3.xml", "error"=>{}},
{"name"=>"Red_Hat_Enterprise_Linux_7.xml", "error"=>{}}]}},
"queue"=>
"reserved_resource_worker-2@sat-r220-06.lab.eng.rdu2.redhat.com.dq",
"state"=>"error",
"worker_name"=>
"reserved_resource_worker-2@sat-r220-06.lab.eng.rdu2.redhat.com",
"result"=>nil,
"error"=>
{"code"=>"PLP0000",
"data"=>{},
"description"=>"Importer indicated a failed response",
"sub_errors"=>[]},
"_id"=>{"$oid"=>"5720e2c9ef75c7ea69aa4f43"},
"id"=>"5720e2c9ef75c7ea69aa4f43"}],
"contents_changed"=>true,
"poll_attempts"=>{"total"=>33, "failed"=>1}}
Related issues
Updated by amacdona@redhat.com almost 8 years ago
- Triaged changed from No to Yes
Updated by dkliban@redhat.com over 7 years ago
- Related to Issue #2274: Uploading duplicate content results in ambiguous error message added
Updated by dkliban@redhat.com over 7 years ago
- Related to Issue #375: Error handling when iso repo sync fails for not providing feed certs does not indicate why its failing. added
Updated by dkliban@redhat.com over 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by dkliban@redhat.com over 7 years ago
I added a couple of issues as related to this issue. However, I suspect we have more issues that are of similar nature. How about we create a separate task to clean up all the importers and distributors to properly propagate errors?
Updated by mhrivnak over 7 years ago
dkliban@redhat.com wrote:
I added a couple of issues as related to this issue. However, I suspect we have more issues that are of similar nature. How about we create a separate task to clean up all the importers and distributors to properly propagate errors?
+1 Since that work is easily shared, making at least one task per project would be a good idea. You could even separate out importer and distributor, but that might be overkill. It would be interesting to see what concrete guidance you can come up with to put in the tasks for what specifically should be done.
Updated by dkliban@redhat.com over 7 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com over 7 years ago
Updated by dkliban@redhat.com over 7 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_rpm:f4469d254df10626dd1db43d94d51eaffe984610.
Updated by semyers over 7 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Problem: ISO Importer reports a vague failure message
Solution: When some downloads fail, raise an exception with the list of all errors collected during the sync.
closes #2006 https://pulp.plan.io/issues/2006