Artifact distribution to execution server keeps showing run button
Article ID: 108853
Updated On:
Products
CA Release Automation - Release Operations Center (Nolio)
CA Release Automation - DataManagement Server (Nolio)
Issue/Introduction
While running a deployment the Run continuously becomes available while the artifacts are trying to distribute to the execution servers. There may or may not be an error stating: Failed to download artifact to retrieval agent
Cause
Artifacts defined in CA Release Automation with the "Store artifact in local repository" option selected may sometimes result in a 404 error when it attempts to upload the artifact. If you encounter this specific problem then you should see the following messages in your management servers nolio_dm_all.log file. If you don't then the root cause might be different. Take a look at the additional information section to see if the problems described in those articles might apply to your situation.
Messages in nolio_dm_all.log file when the root cause identified here is happening:
2018-06-27 22:35:22,172 [http-nio-80-exec-1] INFO (com.nolio.platform.shared.communication.services.artifacts.repositoryplugins.ArtifactRepositoryPlugin:515) - artifact org.apache.http.client.methods.HttpGet response: HTTP/1.1 404 Not Found [Server: Nexus/2.11.3-01, X-Frame-Options: SAMEORIGIN, X-Content-Type-Options: nosniff, Accept-Ranges: bytes, Content-Type: text/html, Transfer-Encoding: chunked, Date: Thu, 28 Jun 2018 03:35:21 GMT]
Messages in nolio_dm_all.log file when the root cause identified here is happening:
2018-06-27 22:35:22,172 [http-nio-80-exec-1] INFO (com.nolio.platform.shared.communication.services.artifacts.repositoryplugins.ArtifactRepositoryPlugin:515) - artifact org.apache.http.client.methods.HttpGet response: HTTP/1.1 404 Not Found [Server: Nexus/2.11.3-01, X-Frame-Options: SAMEORIGIN, X-Content-Type-Options: nosniff, Accept-Ranges: bytes, Content-Type: text/html, Transfer-Encoding: chunked, Date: Thu, 28 Jun 2018 03:35:21 GMT]
Environment
CA Release Automation 6.2.0.3017
Resolution
There are two things you can do to remedy this problem:
- Upgrade to CA Release Automation version 6.6. Some best practices for upgrading to 6.6 can be found here: 6.6 Upgrade Best Practices
- Unset the "Store artifact in local repository" option.
Additional Information
Other root causes for problems with artifact distribution can be found here:
Failed to download artifact to retrieval agent
Failed to distribute artifact to execution server
Failed to download the artifact. The requested resource is not available.
Cannot deploy applications as the artifact cannot be sent to the execution server.Intermittent deployment halted, distribution of artifacts fails
Unable to transfer artifacts larger than 1 GbDeploying folder as artifact fails with 'Error storing the artifact...'
Feedback
Yes
No
Powered by
