openshift-ansible: Unable to start SSO application

Unable to launch application using the sso image from the xPass image stream

Version

openshift-ansible-3.3.4-1-804-g767fa52
ansible 2.1.0.0

Steps To Reproduce

oc cluster up
oc login -u system:admin
oc create -n openshift -f jboss-image-streams.json
oc login -u developer
oc new-app --docker-image registry.access.redhat.com/redhat-sso-7/sso70-openshift --name=ssoservice

Current Result

Can not launch the application with following error:

18:08:00,877 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/eap/standalone/configuration/standalone_xml_history/current to /opt/eap/standalone/configuration/standalone_xml_history/20161117-180800876
	at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638)
	at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470)
	at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
	at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:449)
	at org.jboss.as.server.ServerService.boot(ServerService.java:368)
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
	at java.lang.Thread.run(Thread.java:745)

18:08:00,877 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Expected Result

The application should start.

Additional Information

Work around is to actually delete <kbd>/opt/eap/standalone/configuration/standalone_xml_history/current</kbd> directory from the image/container.
This can be done by updating the <kbd>/opt/eap/bin/openshift-launch.sh</kbd> file:

# Add following command at the start of the file:
rm -fr $JBOSS_HOME/standalone/configuration/standalone_xml_history/current

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 23 (13 by maintainers)

Commits related to this issue

Fix SSO pod startup issues due to xml history mount (#858) * Add update of sso templates to cns ocp implementation * Add workaround for https://github.com/openshift/openshift-ansible/issues/2823 * ... — committed to openshift/openshift-ansible-contrib by glennswest 7 years ago
Add workaround for the weird `standalone_xml_history` issue The workaround was adapted from: https://github.com/openshift/openshift-ansible/issues/2823 Fixes: #30 — committed to snowdrop/secured-example by geoand 6 years ago
Fix SSO pod startup issues due to xml history mount (#858) * Add update of sso templates to cns ocp implementation * Add workaround for https://github.com/openshift/openshift-ansible/issues/2823 * ... — committed to jaywryan/openshift-ansible-contrib by glennswest 7 years ago

Most upvoted comments

Another workaround is to create a persistent volume claim in the deployment config like below:

# Create a persistent volume claim in the deployment config using the command below
$ oc volume dc/sso --add --claim-size 512M --mount-path /opt/eap/standalone/configuration/standalone_xml_history --name standalone-xml-history

kunallimaye on Nov 7, 2017