Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
2.7.2
-
None
Description
Current Situation
- After upgrading from JS7 release 2.7.1 to a later release, jobs are not executed on the assigned Subagent Cluster. The configuration is working as expected in release 2.7.1, but after the upgrade, the same job can be executed on a Subagent that is not a member of the assigned Subagent Cluster.
- The reason being an internal change of an object name in the Controller's and Agent's journal: starting from release 2.7.2 the object name subagentSelectionIdExpr is changed to subagentBundleIdExpr. The problem is caused by a flawed compatibility function, that leaves the original object name unchanged. As a result the object is not identified and an arbitrary Subagent is selected for execution of the job.
- The problem affects the Controller and Director Agents in an Agent Cluster. The problem does not affect Standalone Agents and Subagents in an Agent Cluster. The problem does not affect JOC Cockpit.
Desired Behaviour:
- The Controller and Agents should provide compatibility for Subagent Cluster configurations created with releases prior to 2.7.2..
Workaorund
- The issue is resolved by redeploying workflows after upgrading to a release after 2.7.1.
Steps to Reproduce:
- Configure multiple Subagent Clusters in a JS7 2.7.1 environment.
- Assign a job one of the Subagent Clusters.
- Execute the workflow in JS7 2.7.1 → the job runs correctly on the assigned Subagent Cluster.
- Upgrade the environment to JS7 2.7.2 or later without modifying the Subagent Cluster configuration.
- Execute the same workflow again. The job executes on a Subagent that is not a member of the assigned Subagent Cluster.
Maintainer Notes
- For branch 2.7 a patch release 2.7.5.1 will be made available by Sep 1st 2025.
- A patch is available for release 2.7.5 with Controller and Director Agents. No need to apply the patch to Standalone Agents and to Subagents in an Agent Cluster that are not affected.
- Controller
- Director Agent
- A patch is available for release 2.8.0 with Controller and Director Agents. No need to apply the patch to Standalone Agents and to Subagents in an Agent Cluster that are not affected.
- Controller
- Director Agent