Question

14
Replies
2296
Views
AshishV5 Member since 2018 1 post
Aaseya IT Services Pvt. Ltd.
Posted: 2 years ago
Last activity: 2 years 2 months ago
Closed
Solved

Devops pipeline executed, getting error while deploying to QA "Unable to fetch artifact from repository. Invalid artifact type passed"

Hi All,

I am working on PEGA Dev ops using deployment manager in version 7.3.1, i am able to configure and create a pipeline, but it is failing in QA with error "Unable to fetch artifact from repository. Invalid artifact type passed". i am not getting any error while tracing and all REST call (Publish/restorepoint/deploy) executed with SUCCESS response.

FYI, Orch/Sor/Dev systems are same as Dev system and candidate system is QA. i am using Pega repository for both Dev and Prod.

as per my analysis,

using pipeline, product file is getting published in DEV repository and i have validated the zip in service export directory as well.

Based on below pipeline execution logs deploy task has been completed, while publishing the status to Release manager, it is getting failed.

=============== Beginning of remote server logs for task: deploy, Server:Quality Assurance ===============
2018-03-07 03:34:20,089 [PegaRULES-Batch-5] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution started for task type: deploy
Request object: {
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"<Application Name>"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"<Build Artifact name>.zip"
,"pyCallBackURL":"<Server URL>/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD ABC-46"
,"pyRepositoryName":"ABCDevRepository"
,"pyDependencies":[ ]
}

2018-03-07 03:34:20,716 [PegaRULES-Batch-5] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution completed for task : deploy
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"<Application name>"
,"pyApplicationVersion":"01.01.01"
,"pyBuildArtifactName":"<Build Artifact name>.zip"
,"pyCallBackURL":"<Server URL>/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD ABC-46"
,"pyRepositoryName":"ABCDevRepository"
,"pyStatusMessage":"Unable to fetch artifact from repository. Invalid artifact type passed"
,"pyStatusValue":"FAILED"
,"pyDependencies":[ ]
}

=============== End of remote server logs for task: deploy, Server:Quality Assurance ===============

and as per below PEGA logs getting below exceptions:

1. 2018-03-08 03:11:48,675 [ PegaRULES-Batch-46] [ STANDARD] [ ] [ ABC:01.01.01] ( internal.mgmt.Executable) ERROR - Exception
com.pega.pegarules.pub.PRRuntimeException: /www/DEV/temp/StaticContent/global/ServiceExport (Is a directory)

Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyCallBackURL":"<Server URL>/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD ABC-51"
,"pyStatusMessage":"Internal processing error.** /www/DEV/temp/StaticContent/global/ServiceExport &#40;Is a directory&#41;"
,"pyStatusValue":"FAIL"
}

2. File not found exception

at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
Caused by: java.io.FileNotFoundException: /www/DEV/temp/StaticContent/global/ServiceExport (Is a directory)

3. not passing artifact type value

2018-03-08 03:11:52,603 [http-nio-8070-exec-8] [ STANDARD] [ ] [easeManager:01.01.01] ( internal.mgmt.Executable) ERROR <DEV Node>|<IP>|Rest|cicd|v1|task|AWRIGT9E4AOTJX0KOHKRIEJY75Q0G3VFD - Exception
com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank. page: BuildPage.pyBuildArtifacts. Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)

if anyone face same type of issues, or aware of this issue, please share your feedback.

Regards,

Ashish Verma

DevOps
Moderation Team has archived post
Share this page LinkedIn