Che using an external keycloak fails to update #19670
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
kind/bug
Outline of a bug - must adhere to the bug report template.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
Milestone
Describe the bug
The community operatorhub installplan fails to upgrade from 7.28.2 to 7.29.0 using an external keycloak.
The Che container will never reach ready because of unexpected input from the Keycloak server.
By reviewing the operator installplan log I noted the change to the keycloak auth URL (see below).
By manually editing the checluster keycloak URL (and the subsequent configmap) to the previous URL Che ran fine and install completed (I added '/auth' back to the end). See logs at bottom for the installplan behavior that created this issue.
Che version
7.29.0
Steps to reproduce
Expected behavior
Che upgrades and restarts
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
chectl version
commandEnvironment
Eclipse Che Logs
OperatorHub Log entry:
- "CHE_KEYCLOAK_AUTH__INTERNAL__SERVER__URL": "https://keycloak.dev.domain/auth",
+ "CHE_KEYCLOAK_AUTH__INTERNAL__SERVER__URL": "https://keycloak.dev.domain",
- "CHE_KEYCLOAK_AUTH__SERVER__URL": "https://keycloak.dev.domain/auth",
+ "CHE_KEYCLOAK_AUTH__SERVER__URL": "https://keycloak.dev.domain",
The text was updated successfully, but these errors were encountered: