Pega deployment manager showing waiting
Configured deployment manager 5 in 8.5.2 instance. Pipeline showing waiting since the branch is initiated for merge. No error on running the diagnostics pipeline. No error.
Accepted Solution
Updated: 2 Mar 2022 15:53 EST
Pegasystems Inc.
IN
@HemantM55 Looks like Agent is not picking the tasks , could you please ensure that OrchestratorURL is Saved. Go to Settings->General settings -> Click Save button on top right corner, if you do not click Save OrchestratorURL will not be saved.
Updated: 2 Mar 2022 16:51 EST
Cognizant
IN
@HemantM55 - we are facing the same issue.
PDM 5.5 is deployed on pega platform 8.5.2 and connecting to a candidate system on Pega version 8.6.
The run diagostics is success and we have saved the OrchestratorURL in PDM. Ran tracer and found no error.
However, the deployment is "waiting at step 1". What else could be wrong?
Below is the error in the candidate system:
"DMReleaseAdmin is not present on Candidate system","test":"CONNECTIVITY","troubleShootingTips":"","urlBookmark":"#configauth","urlType":"setting-orchestrator","StackTrace":"","ResponseCode":""},{"ID":"DIAG_009","status":"SUCCESS ","errorMessage":"Development environment was not able to connect to the orchestrator.","description":"Callback n/w issue to orchestrator","test":"CONNECTIVITY","troubleShootingTips":"1.If you are not on Pega Cloud, ensure OrchestratorURL dynamic system setting is correctly configured on Development.\n2.Ports are correctly configured on the orchestrator.\n3.DMAgentUser Operator is enabled on the orchestrator.\n\nIf you are using oAuth2.0 for communication,\n\n 1. Verify if the client credential is updated on DMReleaseAdmin_OAuth2 authentication profile.\n 2. Verify if the access token endpoint URL is correct in DMReleaseAdmin_OAuth2 authentication profile.","urlBookmark":"","urlType":"setting-orchestrator","StackTrace":"","ResponseCode":""}
is DMReleaseAdmin id required in candidate system?
Thanks,
@HemantM55 - we are facing the same issue.
PDM 5.5 is deployed on pega platform 8.5.2 and connecting to a candidate system on Pega version 8.6.
The run diagostics is success and we have saved the OrchestratorURL in PDM. Ran tracer and found no error.
However, the deployment is "waiting at step 1". What else could be wrong?
Below is the error in the candidate system:
"DMReleaseAdmin is not present on Candidate system","test":"CONNECTIVITY","troubleShootingTips":"","urlBookmark":"#configauth","urlType":"setting-orchestrator","StackTrace":"","ResponseCode":""},{"ID":"DIAG_009","status":"SUCCESS ","errorMessage":"Development environment was not able to connect to the orchestrator.","description":"Callback n/w issue to orchestrator","test":"CONNECTIVITY","troubleShootingTips":"1.If you are not on Pega Cloud, ensure OrchestratorURL dynamic system setting is correctly configured on Development.\n2.Ports are correctly configured on the orchestrator.\n3.DMAgentUser Operator is enabled on the orchestrator.\n\nIf you are using oAuth2.0 for communication,\n\n 1. Verify if the client credential is updated on DMReleaseAdmin_OAuth2 authentication profile.\n 2. Verify if the access token endpoint URL is correct in DMReleaseAdmin_OAuth2 authentication profile.","urlBookmark":"","urlType":"setting-orchestrator","StackTrace":"","ResponseCode":""}
is DMReleaseAdmin id required in candidate system?
Thanks,
Meera
Cognizant
IN
Hi Hemant,
DMReleaseAdmin is not present in candidate system but is it required ? As per documentation, candidate system only required dmreleaseadmin authentication profile. Even after creating operator id, the deployment status is still shown as ‘waiting’. Logs are not showing any error but it isn’t working.
Thanks,
Meera