Deployments fail with error "Failed to mount deployment content"
search cancel

Deployments fail with error "Failed to mount deployment content"

book

Article ID: 373107

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

While doing a deployment, which can be a WAR or any other, it fails with the following error message:

Action Description: Run Command Line action has failed. <BR>Return value: 1. Return value is not equal to expected 0<BR>Std out: {"XYZ: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"XYZ: Failed services" => {"jboss.deployment.unit.\"sfg-services.war\".STRUCTURE" => "XYZ: Failed to process phase STRUCTURE of deployment \"sfg-services.war\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: XYZ: Failed to mount deployment content
    Caused by: java.util.zip.ZipException: too many length or distance symbols"}}}}

Environment

Release Automation 6.8 and above

Cause

This issue is caused when a binary is deployed, while the option "Tokenized File Format" is selected:

Having this option selected, it's expected that the file being deployed is in Text format, which is used for token management.

On this case, since the file being deployed is a WAR, it will be treated as a text, converting the binary into a string format, causing the deployment to fail.

Resolution

If a binary is deployed, the option "Tokenized File Format" should never be selected.