AMQ Pod scale-up fail: EAP missing AMQ dependencies

[vap0rtranz]

The AMQ Pod fails to scale up after multiple retries. In Wildfly/EAP logs, server starts but says root.war deploy failed on what looks to be missing AMQ dependencies and a JBoss wrapper gets a TERM signal from somewhere.

Templates:
https://github.com/jboss-fuse/application-templates/blob/master/quickstarts/eap-camel-amq-template.json
https://github.com/jboss-fuse/application-templates/blob/master/fis-image-streams.json

OCP version:
openshift v3.9.25
kubernetes v1.9.1+a0ce1bc657

Log snippet:

20:07:51,779 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT.war")]) - failure description: {
--
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.ActiveMQConnectionFactory"],
--
20:07:52,646 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.2.GA (WildFly Core 3.0.13.Final-redhat-1) started (with errors) in 26752ms - Started 551 of 863 services (21 services failed or missing dependencies, 489 services are lazy, passive or on-demand)
--
ERROR *** JBossAS wrapper process (1) received TERM signal ***