This document describes how to resolve CliqrIgnoreAppFailure parameter failure.
The information in this document is based on CloudCenter 22.214.171.124.
The information in this document is based on these software and hardware versions:
- CloudCenter Manager (CCM) console
- cliqr-cloud-management.jar file
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
When you deploy an instance in CloudCenter, it automatically terminates the Virtual Machine (VM) when it fails to deploy the instance. CloudCenters global parameter CliqrIgnoreAppFailure helps to prevent the VMs to be terminated even when the deployment fails. However, in CloudCenter version 126.96.36.199, VM's terminates even after the CliqrIgnoreAppFailure parameter is enabled.
This article is specific to Cloudcenter 188.8.131.52 and the fix is provided in 4.9 version. In order to workaround this bug, you need to patch the CloudCenter with the attached patch.
Follow these instructions in order to patch the CCM.
Step 1. Log in to CCM with root credentials.
Step 2. Download the cliqr-cloud-management.jar file to /tmp directory.
Step 3.Navigate to /usr/local/tomcat/webapps/ROOT/WEB-INF/lib directory.
Step 4. Move old cliqr-cloud-management.jar to a different directory or rename it as cliqr-cloud-management.jar.orig
Step 5. Copy the patch downloaded from /tmp directory to /usr/local/tomcat/webapps/ROOT/WEB-INF/lib directory
Step 6. Rename the file to cliqr-cloud-managmeent.jar.
Step 7. Change the permission of cliqr-cloud-managmeent.jar to cliqruser:
# chown cliqruser:cliqruser cliqr-cloud-managmeent.jar
Step 8. Edit /usr/local/tomcat/webapps/ROOT/WEB-INF/gateway.properties.
Step 9. Add this line
Step 10. Restart the tomcat service.