Bug 750861 - Need to handle error on trying to export while sync is going on
Summary: Need to handle error on trying to export while sync is going on
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 15:38 UTC by Preethi Thomas
Modified: 2013-09-09 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-21 14:22:52 UTC


Attachments (Terms of Use)

Description Preethi Thomas 2011-11-02 15:38:49 UTC
Description of problem:

repo export blows up with Index error while repo sync is going on,


[root@preethi ~]# pulp-admin repo export --id=f14  -t /tmp/f14 --status
+------------------------------------------+
               Status for f14
+------------------------------------------+
Step: Export in progress (/)

[root@preethi ~]# pulp-admin repo export --id=f14  -t /tmp/f14 -F
Export on repository f14 started
You can safely CTRL+C this current command and it will continue
Step: Export in progress (-)
Traceback (most recent call last):
  File "/usr/bin/pulp-admin", line 23, in <module>
    admin.main()
  File "/usr/lib/python2.7/site-packages/pulp/client/lib/cli.py", line 152, in main
    command.main(self.args[1:])
  File "/usr/lib/python2.7/site-packages/pulp/client/pluginlib/command.py", line 129, in main
    action.main(args[1:])
  File "/usr/lib/python2.7/site-packages/pulp/client/pluginlib/command.py", line 211, in main
    self.run()
  File "/usr/lib/python2.7/site-packages/pulp/client/admin/plugins/repo.py", line 1847, in run
    utils.system_exit(os.EX_DATAERR, _("Error: %s" % e[1]))
IndexError: tuple index out of range

Version-Release number of selected component (if applicable):
root@preethi ~]# rpm -q pulp
pulp-0.0.244-1.fc15.noarch

Comment 1 Jay Dobies 2012-11-21 14:22:52 UTC
This is taken care of by the coordinator in v2. There are no new planned builds for v1 so I'm closing this out.


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