Discussion
Pegasystems Inc.
US
Last activity: 1 Jul 2022 6:30 EDT
Troubleshooting connection issues between Orchestrator and Candidate system, or vice versa
Often times the issue is due to incorrect configuration of the authentication profiles. Try the following suggested steps to address this issues
- Leverage the troubleshooting tips in the diagnostics. There is a lot of useful steps provided and it can guide you as to what the root problem could be.
- Ensure that the DMAppAdmin, DMReleaseAdmin or any other operators specified in the authentication profiles for the environments are enabled.
- Confirm that the passwords and ids of DMReleaseadmin and DMAppadmin authentication profile match the respective operators on the candidate and Orchestrator systems. Often times there are typos in the passwords specified on any of those environments.
- Check whether there is a VPN or firewall that restricts access to the target environment and ensure that the orchestrator environment IP ranges are whitelisted or accessible through the load balancer. Check this in both directions, from the target environment to the orchestrator and vice versa.
Diagnostics fails sporadically with a 500 server error
Message included with the exception is ‘Timed out borrowing service requestor from requestor pool for service package: cicd, timeout set to 10000’.This happens when there is high number of DM users or when requestor pool is not cleared and can be resolved by increasing Pooling settings in cicd service package as per below screenshot.
Diagnostics fails sporadically with a 401 server error
Some users have reported needing to check pre-emptive authentication in DMAppAdmin. This is dependent upon Authentication configuration on the candidate environments and is not a restriction imposed by Deployment Manager.
This is a frequently asked question about Deployment Manager. Find more answers here.
Bradesco Seguros
BR
we are using here in a project, the infrastructure through PegaCloud. Recently, the customer requested blocking of certain IPs to access QA and PRD environments. However, when we configure the Deployment Manager to access these environments, it receives the Http 403 error. We made all the necessary configurations, the same ones that we applied in the development environment, where the connection works correctly. What can be done in this situation? Even if the client requests the blocking of IPs, shouldn't the orchestrator be able to communicate with the QA and PRD environment through PegaCloud?
Pegasystems Inc.
IN
@GuiValino1984 could you please let me know the Authentication profile that is used on the stage ? Also, please ensure that the same OperatorID exists in Candidate and it is pointing to PegaDevOpsFoundation application. I also recommend you to raise a support request for this if it is not resolved
Bradesco Seguros
BR
the solution path we had here was to put the Orchestrator's IP in the list of possible IPs for accessing the QA|UAT environment and with that it worked well
Bradesco Seguros
BR
I would like to share one more important point, on the behavior between the orchestrator and the candidate system.
I performed all the necessary configuration and structured the pipeline to be able to execute the first step, access the development environment and with that to be able to generate the artifact.
Posting the archive resource from agent to orchestrator failed. Error: while creating the archive.
what can I check so that it can finally generate the final file referring to the Artifact. Is there any role that should be configured in the application that the package is being generated and indicated in the access group?
Bradesco Seguros
BR
Type of Incident:Product Resolution type: Solution Root cause: Pega - Bug Root cause description:
BUG-717375
Solution type: Hot Fix - Shipped Existing Solution description:
Apply HFIX-83364