Identifying and Removing Blocking Processes in CA Release Automation

Products

• CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

A new process is created and executed but immediately enters a Blocked status. In the Release Operations Center (ROC), the execution may appear to be waiting indefinitely without progressing, or it may only show a list of previously completed processes without executing the current deployment steps.

Environment

Release Automation 6.8.*, 6.9.*

Cause

This issue typically occurs due to Exclusive Execution settings on Server Types.

1. Exclusive Execution: If a Server Type is configured to "Require exclusive execution," any agent assigned to that server type can only run one process at a time.
2. Hung or Failed-Paused Processes: If a previous process using the same agent is still running, has hung, or is in a "Failed-Paused" state, all subsequent jobs queued for that agent will remain in a Blocked status until the preceding job is finished or removed.

Resolution

1. Log in to the ROC and navigate to Environments > Execution Overview.
2. Look for processes in a Running or Failed-Paused state that utilize the same agents as your blocked process.
3. Identify the specific process and stop/cancel it if it is hung.

 

Following SQL Query could also be used to find the Deployment with jobs in status Running or Failed-Paused

SELECT r.name, r.release_result, r.currentStage, j.process_name, j.title, j.major, j.minor, j.creation_time, j.start_time, j.end_time, j.last_distribution_time, j.purging_status
FROM rc_releases r
LEFT JOIN execution_jobs j ON j.release_id=r.id
WHERE process_name is NOT NULL and j.purging_status IS NULL and j.major<>'Final' and j.minor<>'Finished'
ORDER BY j.creation_time