Question

Pega 7.3.1 - Deployment manager - Pipeline issue

When we try to deploy app from DEV to SIT using pipleline, seeing the below issue logs. Please advice on how to fix it.

[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (L.Embed_Repository_Type.Action) INFO Admin.Deployme - File URL is : file://repo_cicdrepo:/application/Deployme_01.01.01/Deployme_010101_1/Deployme_010101_1.zip
[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO Admin.Deployme - ####################################FETCH############################
[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO Admin.Deployme - Target File Path # file://web:/StaticContent/global/ServiceExport/Deployme_010101_1.zip
[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO Admin.Deployme - Source File Path # file://repo_cicdrepo:/application/Deployme_01.01.01/Deployme_010101_1/Deployme_010101_1.zip
[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO Admin.Deployme - ####################################FETCH############################
[ PegaRULES-Batch-5] [ STANDARD] [ ] [ Deployme:01.01.01] (apper.Pega_Int_Pipeline.Action) INFO Admin.Deployme - Task execution completed for task : deploy
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"Deployme"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"Deployme_010101_1.zip"
,"pyCallBackURL":"http://10.0.0.9:7004/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD DE-33"
,"pyRepositoryName":"cicdrepo"
,"pyStatusMessage":"Authentication Failed"
,"pyStatusValue":"FAILED"
,"pyDependencies":[ ]
}

Comments

Keep up to date on this post and subscribe to comments

December 6, 2018 - 3:23am

I have orchestration and Development Pega servers in same machine, SIT environment in other machine.
We are using file based repository for CI/CD pipeline.
When i trigger the build manually, it completes in DEV machine and moves to next environment then failing with above mentioned error.
My question is the file based repository supported for DEV OPS CI/CD implemetation. 

December 6, 2018 - 11:07am

File based repository should work in Deployment Manager v2.1.1 for platform version 7.3.1. Based on the log snippet you posted, it looks like there is an authentication failure of some sort. Double check the following, Auth profile for connecting to the SIT (QA) environment.  Repository configuration should also be double checked in the SIT environment, make sure to test the connectivity to ensure that the repository connectivity passes there as well.

December 7, 2018 - 5:11am
Response to Linoy Alexander

Authentication profile was configured properly in Deployment manager. Deployment manager can communicate to SIT server using the authentication profile. SIT environment can connect to its repository, test connection was successful. But when it tries to fetch the zip (RAP) from Deployment manager its failing. I am not sure how to fix it. Please help

December 7, 2018 - 1:23pm
Response to mahendranm2345

A few additional things you can try to pinpoint the issue

a) This is rather obvious, but ensure that you filesystem location has the appropriate read-write permissions and is accessible. Assuming this is true, then try b) and c)  

b) Ensure that SIT to filesystem repo connections are valid, beyond just these Test Connectivity - Try to import the archive directly from the repository in the SIT environment? This would require you to login to the SIT environment, use the import wizard, select repository as the source and then you File system based repository. 

c) Ensure that dev environment can publish to the filesystem  - Check that you are able to successfully publish or export to that repository. Confirm that the dev environment is actually writing the archive to the filesystem either through the Deployment Manager or directly by using the export wizard which will give you an option to export to the repository

 

 

 

 

December 9, 2018 - 11:28pm
Response to Linoy Alexander

Hi Linoy,

Thanks for your reply.

Above mentioned all the suggestions are verified. Everything looks good in my system. I have attached screenshots for the same.

a. File permission are good. Please refer the screenshot.

b. I can import the archive directly from the repository in the SIT env. by login to UI.

c. I have tried to export the application to repository in DEV env, it worked fine. I can see the file in repo directory.

Please let me know if require any logs.

Thanks

Mahendran M

 

December 10, 2018 - 3:08am
Response to mahendranm2345

Hi Linoy.

We notice that target file path and source file path are different in the logs. But in my repository configuration for both DEV and SIT mentioned the same path.Also target server (SIT- on a separate server) doesn't have this file path.

Is there any configuration that we need to check for this one.

Target File Path # file://web:/StaticContent/global/ServiceExport/Deployme_010101_1.zip

Source File Path # file://repo_cicdrepo:/application/Deployme_01.01.01/Deployme_010101_1/Deployme_010101_1.zip

Pega
December 10, 2018 - 6:05am

Hi

Could you please check that repositories on orchestrator and candidates are pointing to correct repositories. Looks like there is some mismatch between candidates and orchestrator.

Thanks

 

 

December 10, 2018 - 11:41am
Response to gurrp1

Exactly as suggested by gurrup1, there seems to be some mismatch in the repository configuration in the orchestrator instance (Deployment Manager). Make sure this configuration is exactly the same across all the environments including the orchestrator. It is especially important that the repository names (and type of repository) are the same across all instances. See bullet point 2 in the Step 2c of creating repositories  .

December 12, 2018 - 6:03am
Response to Linoy Alexander

Hi Linoy,

I have recreated orchestrator instance and triggered manual build. This time its failing with below error. 

Error - java.io.FileNotFoundException - the given file path is not valid.

File path exist in the orchestration instance (linux system) and its with full permission (777).

For the file based respository, do we need to configure shared folder in orchestrator server and make it available to SIT environment? 

Please check and suggest.

file://repo_CICDRepo:/application/DMSample_01.01.01/DMSample_010101_2/DMSample_010101_2.zip

 

 

 

2018-12-12 08:59:54,638 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (apper.Pega_Int_Pipeline.Action) INFO   Admin.Deployme - Task execution started for task  type: deploy

 Request object: {

"pxObjClass":"Pega-Int-Pipeline"

,"pyApplicationName":"DMSample"

,"pyApplicationVersion":"01.01.01"

,"pyBuildArtifactName":"DMSample_010101_2.zip"

,"pyCallBackURL":"http://*.*.*.*:7004/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"

,"pyID":"PEGA-PIPELINE-CD DM-6"

,"pyRepositoryName":"CICDRepo"

,"pyDependencies":[ ]

}

 

2018-12-12 08:59:54,645 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (L.Embed_Repository_Type.Action) INFO   Admin.Deployme - File URL is : file://repo_CICDRepo:/application/DMSample_01.01.01/DMSample_010101_2/DMSample_010101_2.zip

2018-12-12 08:59:54,645 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO   Admin.Deployme - ####################################FETCH############################

2018-12-12 08:59:54,645 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO   Admin.Deployme - Target File Path # file://web:/StaticContent/global/ServiceExport/DMSample_010101_2.zip

2018-12-12 08:59:54,645 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO   Admin.Deployme - Source File Path # file://repo_CICDRepo:/application/DMSample_01.01.01/DMSample_010101_2/DMSample_010101_2.zip

2018-12-12 08:59:54,645 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (h.Embed_Repository_Type.Action) INFO   Admin.Deployme - ####################################FETCH############################

2018-12-12 08:59:54,650 [   PegaRULES-Batch-1] [  STANDARD] [                    ] [   Deployme:01.01.01] (.repository.ArtifactRepository) ERROR  Admin.Deployme - error in fetching file

java.io.FileNotFoundException: The given path file://repo_CICDRepo:/application/DMSample_01.01.01/DMSample_010101_2/DMSample_010101_2.zip was not valid.

        at com.pega.pegarules.data.external.access.artifact.repository.ArtifactRepository.fileCopy(ArtifactRepository.java:357) ~[prenginext.jar:?]

        at com.pega.pegarules.data.external.access.artifact.repository.ArtifactRepository.fetchArtifact(ArtifactRepository.java:98) ~[prenginext.jar:?]

        at com.pega.pegarules.deploy.internal.PRRuleMgmtUtilsImpl.fetchArtifact(PRRuleMgmtUtilsImpl.java:1756) ~[prprivate.jar:?]

        at com.pegarules.generated.activity.ra_action_pxfetch_cc12e0ea21bd32a66925609bb7be52e2.step3_circum0(ra_action_pxfetch_cc12e0ea21bd32a66925609bb7be52e2.java:301) ~[?:?]

        at com.pegarules.generated.activity.ra_action_pxfetch_cc12e0ea21bd32a66925609bb7be52e2.perform(ra_action_pxfetch_cc12e0ea21bd32a66925609bb7be52e2.java:90) ~[?:?]

        at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3597) ~[prprivate.jar:?]

        at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10845) ~[prprivate.jar:?]

December 13, 2018 - 11:00am
Response to mahendranm2345

There seems to be some mismatch between the repository configuration on the deployment manager and the one on the target systems in the pipeline. Double check this again, but it is also likely that someone from DM support should get on a call with you and walk through everything to further diagnose this issue. Please contact DeploymentManagerSupport@pega.com and we can arrange a time to meet.