Discussion
Pegasystems Inc.
US
Last activity: 6 Nov 2023 18:04 EST
After upgrade deployment manager to 4.5, repository diagnostics is failing
After upgrade deployment manager to 4.5, repository diagnostics is failing with error 'The artifact cannot be read from the repository'.
This issue is often seen if the candidate systems are in an older version of PegaDevOpsFoundation, such as when you are using the lastest version of Deployment Manager to manage pipelines where the target environments are on platform 7.4.
- If candidates are not upgraded to PegaDevopsFoundation 4.5 and browse artifacts displays the related artifacts, then user can safely ignore this error.
- This issue has been fixed in Deployment Manager version 4.6
- Note that: Deployment Manager is still backward compatible in terms of functionality, but in diagnostics check on orchestrator repository is failing due to additional checks made on new version. This issue will be fixed if candidates are upgraded to PegaDevopsFoundation 4.5.
This is a frequently asked question about Deployment Manager. Find more answers here.
Updated: 30 Dec 2022 4:09 EST
Capgemini
IN
@RyanFeeney In PegaDevopsFoundation 5.5 also I am facing the same error where my target environments are upgraded to 8.7...could you please help me how to resolve
Areteans
AU
were you able to resolve this ?
Areteans
AU
We resolved this issue.
We are using a NAS folder as a repository and mounted a server folder to this NAS folder.
For the NAS folder that we requested to create, the storage team did not provide full access to the Linux user. Note: We are using Linux along with Apache as an application server. The Linux user that initiated the server, did not have full access to the NAS folder, so we were getting the above error.
We requested the storage team to provide complete access to the Linux user and we were able to connect successfully.
Blue Rose Technologies
NL
@PriyadharshiniM Is this resolved? If yes please let us know the solution
Updated: 2 Nov 2023 8:43 EDT
Pegasystems Inc.
US
@Deepthi Chivukula @PriyadharshiniM the issue described in the original post was due to a very specific upgrade problem.
If you are seeing this error message now, you should make sure that all of the environments are configured to point to the same dev repository, and the dev environment has the privilege to publish to that respository. What the diagnostics tool is doing here is telling the Dev environment to publish a small file, and then confirming that the other non-dev environments can read that same file. This validates that the run-time behavior will work properly.
Hope this helps. Let me know if you have any further questions.