Automic CDA 12.3 - can assign agent to deployment target
Article ID: 193088
Updated On:
Products
Issue/Introduction
After upgrading ARA to version 12.3 we cannot assign agents to deployment target, despite that agent is visible in the automation engine in client 0 and deployment client (xxxx). We cannot see any assigned agent is available in the list.
Environment
Release : 12.3
Component : CONTINUOUS DELIVERY DIRECTOR
Cause
The log had the following messages
2020-xx-xx 00:00:14,605 [84(ARA/xxxx)] WARN StaticVaraGetter - Could not get values from vara object PCK.AUTOMIC_PROVISIONING.PRV.PROVISIONING_REGISTRY from AE. Object PCK.AUTOMIC_PROVISIONING.PRV.PROVISIONING_REGISTRY is missing or invalid
2020-xx-xx 00:02:25,686 [110(ARA/xxxx)] ERROR RM.PeriodicTasks - Error processing periodic task 'AgentTracker'
Ventum.Bond2.Services.AutomationEngine.Exceptions.AeRestException: Status code:0. Request resource:system/agents. Response:
at Ventum.Bond2.AERest.AeRestClient.Execute[T](AeRestRequestBase`1 aeRequestBase) in C:\BuildAgent\work\bondrelease\10.0.2\Projects\Ventum.Bond2.AEBridge\AERest\AeRestClient.cs:line 29
Resolution
Installed the missing package
Corrected the customer config in the WebUI folder (Automic\Release.Manager\WebUI\customer.config).
<restApi uri="http://localhost:8088" />
This points to the JCP running on the automation engine
The URL can be found in the jcp log as follows.
REST Endpoint registered as http://xxxxxxx:8088
Once this was corrected agents were discovered without issues.
Additional Information
Feedback
