Component Workflow does not update its status after the Application's Workflow is finished

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Affects Release version(s): 6;7

Error Message :
N/A

When executing an Application Workflow, Components installed on the Deployment Target become stuck in an 'In Progress' status.  

This occurs when failed Components which are set to be skipped (and are skipped) and the remainder of the Workflow continues to process and finishes, but the failed skipped Components remain in an 'In Progress' state on the Deployment Target.

Investigation

1. Run a deployment workflow consisting of several components that will contain failures during the execution.
2. The failures during the execution are displayed similar to this:

<Please see attached file for image>

3. Set the failed Components to skip so that the remainder of the Workflow will continue to process.
4. Cancel the component workflow so that nothing else executes from that component and unblock it so that it will continue to the next component workflow.
5. The deployment will finish and the status will be set to “Finished” as seen below.

<Please see attached file for image>

6. Going to the Applications page will show ARA Components that are still in an "In Progress" status.

<Please see attached file for image>

<Please see attached file for image>

 

Environment

OS: Windows Server 2012

Cause

Cause type:
Defect
Root Cause: The status of Component was shown incorrectly in the application's overview.

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Release.Manager 7.0.2 - Available
Release Manager 6.0.4 - Available

Additional Information

Workaround :
N/A