Question
Infosys Limited
IN
Last activity: 28 Sep 2022 4:31 EDT
Deployment Manger- Candidate Environment not connected to Orchestrator
Hello All,
We have set up the Deployment Manger in internal cloud Instance 8.5 as Orchestrator System and 8.6 as a Candidate System and done all the Configuring and running pipelines with Deployment Manager. While running the Diagnosis we have found this error. Please, let me know if any solution for this.
Both 8.5 and 8.6 setup are available in same cloud VM. We are able to successfully establish connection between 8.5 and 8.6 application via standard REST Services. But it is not able to connect through Deployment Manager.
Also find the screenshot of the error and Document of downloaded log.
Pegasystems Inc.
SE
From 5.4 you might need to force OAuth authentication instead of SA Authentication, I had to set this DSS on candidate and orchestrator systems.
PegaDevopsShared • deploymentmanager/security/authentication/oauth/enabled = true
LTIMindtree
SA
We have recently faced the similar error and did lot of analysis but could not resolve. Issue occured when we started upgrading DEV enviornment from 8.3 to 8.6.0. When we finished upgrading all the environments to same version along with DMGR, they started working back again. Pega GCS also could not find the root cause earlier.
But as per my experience and Knowledge, it's evident and indeed to maintain same version of platform required to connect with Deployment Manager to all other environments.
Just try to maintain the same platform version and check if the Pipelines started working in Deployment manager.
Note: Please accept the solution if it woked for you.