000038362 - 'customizeACM.sh -d' fails with 'Undeploy failed:' error  in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jan 20, 2020•Last modified by RSA Customer Support Employee on Apr 3, 2020
Version 4Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000038362
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
IssueRunning customizeACM.sh -d on a standalone server in RSA Identity Governance & Lifecycle  fails with:
 

Creating aveksa.ear file for deployment
      [zip] Building zip: /tmp/customizeACM/aveksa.war
      [zip] Building zip: /tmp/customizeACM/aveksa.ear
     [copy] Copying 1 file to /home/oracle/archive

Undeploying current ear...
Undeploy failed: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => 
{"Operation step-1" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"aveksa.ear\")]' not found"}}

Deploying new customized ear...    this may take a while...
Exception encountered while deploying Aveksa.ear
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => 
{"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE" => 
"org.jboss.msc.service.StartException in service jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE: 
WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"aveksa.ear\"
    Caused by: org.jboss.msc.service.DuplicateServiceException: 
Service jboss.module.spec.service.\"deployment.jboss-logging-3.3\".main is already registered"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}


Aveksa.ear deployment failed after 1 minutes, 45.208 seconds

Updating CURRENTLY_DEPLOYED_ARCHIVE to aveksa_7.1.1_161195_P04-2020-Jan-20-9.31.ear

aveksa_7.1.1_161195_P04-2020-Jan-20-9.31.ear archived

An error occured in the customizeACM command : error code 5


If you encounter this error installing an RSA Identity Governance & Lifecycle patch, please see related RSA Knowledge Base Article 000038350 -- Patch/upgrade fails with 'Error deploying the ear file' error in RSA Identity Governance & Lifecycle for resolution.
 
CauseThe key error here is:
 
{"Operation step-1" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"aveksa.ear\")]' not found"}}
 

The aveksa.ear file cannot be found. The reason for this error is that the deployed aveksa ear file has a filename other than aveksa.ear.

By default, the RSA Identity Governance & Lifecycle installation, patch/upgrade and customizeACM.sh processes automatically deploy the ear file with the name aveksa.ear and expect the name of the ear file to be aveksa.ear when they go to undeploy the ear.

In cases where the ear file has been deployed manually, it is possible to deploy the ear file with a name other than aveksa.ear. In this case future patching, upgrading and customization of the ear file will fail. 
 
Resolution

Redeploy the current ear file as aveksa.ear and re-run customizeACM.sh.



  1. Login as the oracle user
  2. Determine the name of the currently deployed ear file:


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deployment-info"


You will see output similar to the following:



NAME                                          RUNTIME-NAME                                  PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear                         aveksaWFArchitect.ear                         true       true    OK
<name other than aveksa.ear>                  <name other than aveksa.ear>             true       true    OK


This is the reason for the failure. The name should be aveksa.ear.


  1. Undeploy the ear file.


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy <name of deployed aveksa ear file>"


  1. Deploy the same ear file as aveksa.ear.


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deploy $AVEKSA_HOME/archive/<name of aveksa ear file to be deployed>
--name=aveksa.ear --runtime-name=aveksa.ear"


  1. Check that the aveksa.ear file deployed correctly.


NAME                   RUNTIME-NAME          PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear aveksaWFArchitect.ear  true       true    OK
aveksa.ear            aveksa.ear             true       true    OK


Now the current ear file is deployed with the name aveksa.ear so customizeACM.sh will be able to find and undeploy the current ear file.


  1. Run customizeACM.sh again.


cd $AVEKSA_HOME/deploy
./customizeACM.sh -c


  1. Make customizations and then deploy the new customized ear file:


./customizeACM.sh -d

 

To avoid the problem in the future:


If you are deploying the ear file manually and not through patching, upgrading or customizeACM.sh, ensure that the ear file is deployed as aveksa.ear by following the instructions in RSA Knowledge Base Article 000038351 -- How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle.
 
Notes

 

Attachments

    Outcomes