[Pulp-list] Errors syncing rhel5 distributions

[Alan Evangelista]

On 09/26/2014 03:29 PM, Baird, Josh wrote:
> jbaird at fc-d1pulp01:~$ ^C
> jbaird at fc-d1pulp01:~$ cat ~/.pulp/admin.log
> 2014-09-26 12:55:11,928 - ERROR - Client-side exception occurred
> Traceback (most recent call last):
>    File "/usr/lib/python2.6/site-packages/pulp/client/extensions/core.py", line 478, in run
>      exit_code = Cli.run(self, args)
>    File "/usr/lib/python2.6/site-packages/okaara/cli.py", line 974, in run
>      exit_code = command_or_section.execute(self.prompt, remaining_args)
>    File "/usr/lib/python2.6/site-packages/pulp/client/extensions/extensions.py", line 224, in execute
>      return self.method(*arg_list, **clean_kwargs)
>    File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/sync_publish.py", line 101, in run
>      status.display_group_status(self.context, self.renderer, task_group_id)
>    File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 64, in display_group_status
>      _display_status(context, renderer, task_list)
>    File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 96, in _display_status
>      _display_task_status(context, renderer, task.task_id, quiet_waiting=quiet_waiting)
>    File "/usr/lib/python2.6/site-packages/pulp/client/commands/repo/status/status.py", line 123, in _display_task_status
>      renderer.display_report(response.response_body.progress)
>    File "/usr/lib/python2.6/site-packages/pulp_rpm/extension/admin/status.py", line 77, in display_report
>      self.render_distribution_sync_step(progress_report)
>    File "/usr/lib/python2.6/site-packages/pulp_rpm/extension/admin/status.py", line 160, in render_distribution_sync_step
>      'message' : error[1]['error_message'],
> KeyError: 'error_message'
>

I do not know about your specific error, but I got a similar exception 
when trying to import a corrupted rpm.
Pulp should handle RPM repository sync errors nicely instead of 
breaking. Is there a bug opened somewhere for
fixing it?


Regards,
Alan Evangelista