New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions are deleted sequentially #3

Closed
stdevel opened this Issue Jul 27, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@stdevel
Owner

stdevel commented Jul 27, 2014

Actions are currently deleted sequentially which can cause problems if you're deleting a lot of actions (due to flooding).

As the Spacewalk API call schedule.deleteActions() also supports deleting multiple actions it would be better to create one deletion request including all the action IDs.

@stdevel stdevel added the bug label Jul 27, 2014

@stdevel stdevel self-assigned this Jul 27, 2014

stdevel added a commit that referenced this issue Jul 28, 2014

Update arsa.py
fixed issues #2 #3 and #4
removed doubled searching for actions
added workaround for deleting huge amounts of actions (actions are deleted in 100 action chunks, added 0.5s delay to avoid "500 Internal Server Error" messages - thanks for hint, James Radtke - https://access.redhat.com/comment/792363#comment-792363)
@stdevel

This comment has been minimized.

Show comment
Hide comment
@stdevel

stdevel Jul 28, 2014

Owner

Fixed in commit ac4078b

Owner

stdevel commented Jul 28, 2014

Fixed in commit ac4078b

@stdevel stdevel closed this Jul 28, 2014

stdevel added a commit that referenced this issue Nov 24, 2015

Update arsa.py
Added support for newer Spacewalk releases - see issue #3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment