Bug 477228 - Unable to cancel actions using schedule.cancelActions
Unable to cancel actions using schedule.cancelActions
Product: Spacewalk
Classification: Community
Component: API (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brad Buckingham
Red Hat Satellite QA List
Depends On:
Blocks: space04
  Show dependency treegraph
Reported: 2008-12-19 13:44 EST by Brad Buckingham
Modified: 2009-01-22 11:31 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-22 11:31:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Exception details from catalina.out (15.16 KB, application/octet-stream)
2008-12-19 13:44 EST, Brad Buckingham
no flags Details

  None (edit)
Description Brad Buckingham 2008-12-19 13:44:27 EST
Created attachment 327482 [details]
Exception details from catalina.out

Description of problem:

Attempting to cancel an action using the schedule.cancelActions() api generates an exception that is thrown back to the user as well as logged in catalina.out.  The exception generated is new since the integration with cobbler and is related to a kickstart query.

See attachment for the detailed error from catalina.out.

Version-Release number of selected component (if applicable):
Testing w/ latest git master as of Dec 19.

How reproducible:

Steps to Reproduce:
1. schedule an action to 
(e.g. client.system.scheduleHardwareRefresh(key,1000020124, <earliest>))
2. attempt to schedule the action using the api:
client.schedule.cancelActions(key, [<actionId>])

Actual results:
Exception generated (however, action is canceled)

Expected results:
Action cancelled without exception

Additional info:
See attachment
Comment 1 Brad Buckingham 2009-01-09 18:40:46 EST
git commit: 5273454049014a5be9ed73b689c4d53115295bec

The ActionManager.cancelAction was deleting the ServerAction before it was finished using it.  Basically, it would delete the ServerActions then perform action.getServerActions resulting in an empty list.  When this empty list was passed to KickstartFactory.failKickstartSessions, the hibernate query could generate an exception because it expected the servers collection (i.e. list passed) to have contents.

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