[
https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug...
]
Jean Francois Denise commented on WFCORE-5216:
----------------------------------------------
[~davykoravand], I can reproduce your problem with latest wildfly 22 locally built.
Actually the fix is different for your issue.
You will notice that JAVA_OPTS is not quoted:
https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/com...
It needs to be quoted, would you mind log a different bug? I would prefer to separate the
2 issues.
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
(v8.13.1#813001)