-
Bug
-
Resolution: Done
-
Critical
-
2.4.0.GA, 2.5.0.GA, 2.5.1.GA
-
None
-
False
-
False
-
Undefined
-
-
CRW 2.5 (and 2.5.1) are not installing well via CLI on OCP 3.11 (no OLM).
When installation is attempted, the keycloak pod does not start. The log reveals:
time="2020-12-23T19:12:09Z" level=error msg="Stderr: Logging into http://0.0.0.0:8080/auth as user admin of realm master\nFailed to create config file: /?/.keycloak/kcadm.config\nNo server specified. Use --server, or 'kcadm.sh config credentials or connection'.\n"
The same behavior can be seen on a terminal in the keycloak pod:
sh-4.4$ /opt/eap/bin/kcadm.sh config credentials --server http://0.0.0.0:8080/auth --realm master --user admin --password admin && /opt/eap/bin/kcadm.sh update realms/master -s sslRequired=none
Logging into http://0.0.0.0:8080/auth as user admin of realm master
Failed to create config file: /?/.keycloak/kcadm.config
Possibly of interest:
The 'auth' configuration section of the CheCluster differs significantly when comparing CRW 2.5 on OCP 4.x vs. 3.11/no-OLM. As an example,
OCP 4 (which installs well) uses spec/auth/identityProviderSecret
OCP 3.11 (no OLM, does not install well) has spec/auth/identityProviderPassword, etc.