I believe the ability to select MULTIPLE systems for a package action and link that with an arbitrary script on ALL those selected systems (such as a post-update reboot) was new in spacewalk 2.0 (in prior versions, it was only possible to link a package action with a remote command on one system at a time).
It seems that the problem I'm encountering is directly related to this new functionality, in that I am unable to CANCEL "linked" actions that were set up IN BULK. (Regardless of whether I try to cancel individual actions, individual systems, all events together, via GUI, or via spacecmd). The reboots need to be cancelled, so I'm guessing I'll have to DELETE the systems from spacewalk and re-add them. Any other ideas, short of this drastic action? Andy On 2/24/14 4:45 PM, "Andy Ingham" <[email protected]> wrote: Either in the GUI or via spacecmd. spacecmd {SSM:0}> schedule_cancel 30953 30741 30740 30739 30738 30737 30736 ERROR: redstone.xmlrpc.XmlRpcFault: unhandled internal exception: null I've tried restarting both the spacewalk stack AND postgres Errors in /var/log/tomcat6/catalina.out seem to indicate it is unhappy about the fact that the events are (package updates & arbitrary scripts) scheduled together. I REALLY need to be able to cancel these events sometime in the next 24 hours. Is there any way to force them to clear? I just upgraded to Spacewalk 2.0 (still with a local postgres 8.4 backend) Help! Andy _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
