[
https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug...
]
Jean Francois Denise commented on WFCORE-5216:
----------------------------------------------
To reproduce the problem escape the env variables: oc set env dc/helloworld
JBOSS_MODULEPATH=\${JBOSS_HOME}/modules:\${HOME}
More generally, do we want to fix this problem? The use-case seems very un-common.
[~jmesnil]?
I we think that we need to fix this problem, then, I think that it should be solved at the
CLOUD level, not at the wildfly-core level.
One solution would be to patch the jboss-clis.sh script (we are already doing that in our
images) to add the following line:
JBOSS_MODULEPATH=$(eval "echo $JBOSS_MODULEPATH")
To force evaluation of the env variable in the script.
EAP Pod fails to start when env
JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set
-------------------------------------------------------------------------------------
Key: WFCORE-5216
URL:
https://issues.redhat.com/browse/WFCORE-5216
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Priority: Major
Since JBoss EAP 7.3 for OpenShift, if environment variable
JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via
DeploymentConfig, EAP Pod fails to start with the following messages:
{noformat}
INFO Duration: 347 milliseconds
ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script.
org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297)
at org.jboss.modules.Main.main(Main.java:371)
{noformat}
This issue does not occur on JBoss EAP 7.2 container.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)