-
Bug
-
Resolution: Done
-
Major
-
RH-SSO-7.6.0
-
False
-
None
-
False
-
-
-
If Release Note Needed, Set a Value
-
Set a Value
-
CIAM Sprint 23
See SSOSUP-345 for original issue report. The issue summary in short being
the "getConfigurationMode: command not found" error is reported is reported
when using the RH-SSO for OpenShift container image under certain circumstances (e.g. performing a S2I build against a git repository). See:
for the exact reproducer.
Possible reason of the bug (after preliminary investigation):
Being the /opt/eap/bin/launch/launch-common.sh script (which contains the definition of the aforementioned getConfigurationMode() function:
[iankko@localhost redhat-sso-7-openshift-image]$ docker run -it registry.redhat.io/rh-sso-7/sso76-openshift-rhel8:7.6 /bin/bash
Unable to find image 'registry.redhat.io/rh-sso-7/sso76-openshift-rhel8:7.6' locally
7.6: Pulling from rh-sso-7/sso76-openshift-rhel8
Digest: sha256:71e89202ccd9bdcd841f2a8a109c89c923626f7aee4c15f5399ee275113b3ba2
Status: Downloaded newer image for registry.redhat.io/rh-sso-7/sso76-openshift-rhel8:7.6
bash-4.4$ cd $JBOSS_HOME
bash-4.4$ grep -rHn 'getConfigurationMode()' *
bin/launch/launch-common.sh:53:function getConfigurationMode() {
might not be included / sourced as needed under certain circumstances.
bash-4.4$ grep -rHn 'launch-common.sh' * bin/launch/login-modules-common.sh:3:source $JBOSS_HOME/bin/launch/launch-common.sh bin/launch/tx-datasource.sh:5:if [ -f $JBOSS_HOME/bin/launch/launch-common.sh ]; then bin/launch/tx-datasource.sh:6: source $JBOSS_HOME/bin/launch/launch-common.sh bin/launch/management-common.sh:3:source $JBOSS_HOME/bin/launch/launch-common.sh bin/launch/datasource-common.sh:6: source $JBOSS_HOME/bin/launch/launch-common.sh
As obviously demonstrated in / by the SSOSUP-345 report, the case of performing S2I build against a git repo isn't one of them. Investigating the issue further.
- is cloned by
-
-
- Closed
-
