While running a deployment I see that my step is getting cancelled without any kind of forewarning or error.
This will happen when the agent is unable to find an appropriate .jar file used by an action in the process. If a missing .jar file is the cause of your cancelled steps then you would see messages similar to the following in the nolio_all.log and/or nolio_action_exe.log file:
2018-07-05 17:07:31,905 [Communication Msg Processor-4] ERROR (com.nolio.platform.shared.datamodel.Action:92) - com.nolio.platform.shared.executables.actions.nexus.DownloadNexusArtifactByUrl
2018-07-05 17:07:31,907 [Communication Msg Processor-4] ERROR (com.nolio.platform.shared.flowcontrol.service.FlowControlService:87) - failed initialize flow for job, jobServerId.
java.lang.RuntimeException: Failed to create action from ActionProxy[null:ActionProxy]
CA Release Automation 6.x and above.
This will likely happen in version 5.x also.
If you see the ClassNotFoundException message followed by "failed to initialize flow for job" message in the agent logs then identify which action pack you need to install. Then install the action pack. Before you install the action pack you must manually download the action pack .jar file and its dependency file (if there is a dependency). You can try checking to see if the action pack is listed as an installed action pack and if it is not then you can install it
Checking For Installed Action Packs
You can check for action packs that the system thinks are installed from both the ROC (Release Operations Center) and Automation Studio.
One reason why a management server may not have the action packs that the CA Release Automation management server thinks it has is migrating your management server. If you stand up a new management server and point it to a database previously used by a management server where the action packs had been installed then the new management server will think (according to the database) that x, y, and z action packs are available. But the files are stored in different folders on the management server so you will need to reinstall the action packs in order for all of your processes to run as expected.
If you have migrated your management server then you should also look to see if there were any custom action packs that might need to be brought over to the new management server. Custom action packs can be found by looking at the list of installed action packs and either: