'Deactivate always' doesn't work in certain situations when HOSTG are used

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

In case a task uses a HOSTG and the task is set to inactive due to some pre-condition, the corresponding HOSTG container stays in status ENDED_SKIPPED and cannot be deactivated.

This waiting is an active state and must first be canceled so that the HOSTG can be deactivated.

Steps to reproduce
* create a HOSTG with multiple active Agents
* create a JOBS using this HOSTG with a simple command like ping/ls/dir
* create a JOBP and add the JOBS as a task
* change the pre-condition of the JOBS in a way that it evaluates to ENDED_SKIPPED (e.g.: IF 1=1 then FINALLY SKIP TASK)
* make sure both, JOBS and JOBP, have 'DEACTIVATE ALWAYS' set
* run the JOBP

=> check Process Monitoring and see the task is stuck in ENDED_SKIPPED
 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Cause

Software Bug

Resolution

The issue has been confirmed to be a bug and will be fixed with a future service pack for Automation Engine V21.0; due to end of maintenance, there will be no fix for 12.3