Question

6
Replies
318
Views
BalajiD0 Member since 2017 3 posts
HCL Technologies Ltd
Posted: 1 year ago
Last activity: 1 year 1 month ago
Closed

Pega Deployment Manager - 8.2 - Stops with : Http status code of call back:301

Please help me with the issue I am facing with Pega Deployment Manager:

I am doing a POC with Pega Deployment Manager (Pega 8.2 and 4.4 deployment manager). For POC purpose I use the same Pega instance for Dev, QA and Stage with HTTP protocol only. I did complete the following (order may be typed differently here):

  1. Created a pipeline with jFrog repo.
  2. Created RMURL DSS with http://localhost:<port>/prweb/PRRestService with ruleset as Pega-DevOps-Foundation
  3. Ensured all Auth Profiles are having the correct password (DMAppAdmin, DMReleaseAdmin, jFrogAuth) and enabled the users after changing the password.
  4. Since it is HTTP only, cleared the check box - "Require TL/SSL ... " in cicd and api service packages
  5. Ran the Diagnose pipeline (attached the screen shot)
  6. Clicked Start deployment
  7. I verified from the folders that the product zip file is created and copied to jFrog repository also.
  8. However the status of the job in Deployment manager shows as ONGOING with no further execution of the stages in the pipeline
  9. The Pega log shows the error as below:

2019-06-26 01:43:50,812 [ PegaRULES-Batch-4] [ STANDARD] [ ] [gaDevOpsFoundation:4] (apper.Pega_Int_Pipeline.Action) INFO DMAppAdmin - Task execution completed for task : publish
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyAccessGroup":"AISample:Administrators"
,"pyApplicationName":"OnBoarding"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"OnBoarding-OnBoarding_010101_18.zip"
,"pyCallBackURL":"http://demos.research.com/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAPCore&FlowActionName=pzPauseTask"
,"pyDoPackage":"true"
,"pyFilePath":"devops/dev/OnBoarding/01.01.01/OnBoarding-OnBoarding_010101_18/OnBoarding-OnBoarding_010101_18.zip"
,"pyID":"PEGA-PIPELINE-CD ON-18"
,"pyPipelineName":"OnBoarding"
,"pyProductName":"AISample"
,"pyProductVersion":"20180807.083250"
,"pyRepositoryName":"JFrogRepo"
,"pyStatusValue":"SUCCESS"
,"pySystemNodeID":"31b730a953128c5792668c0f384f20e3"
,"pyBuildArtifact":{
"pxObjClass":"Data-Artifact"
,"pySize":"1638982.0"
,"pyTargetLocation":"devops/dev/OnBoarding/01.01.01/OnBoarding-OnBoarding_010101_18/OnBoarding-OnBoarding_010101_18.zip"
}
}

2019-06-26 01:43:52,838 [ PegaRULES-Batch-4] [ STANDARD] [ ] [gaDevOpsFoundation:4] (tatus.Pega_Int_Pipeline.Action) INFO DMAppAdmin - Task execution status published by doing call back for task name:publish
Http status code of call back:301
Status message of call back: WARN: HTTP Response code indicated redirectionthe HTTP response code of 301 indicated a server redirection. Redirection is not enabled for this Connector.

DevOps
Moderation Team has archived post
Share this page LinkedIn