Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v7.42.0 OIDC Discovery URL #21057

Closed
jlhawkins-stuff opened this issue Jan 22, 2022 · 6 comments
Closed

v7.42.0 OIDC Discovery URL #21057

jlhawkins-stuff opened this issue Jan 22, 2022 · 6 comments
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@jlhawkins-stuff
Copy link

Describe the bug

Upgrading CHE from 7.40.0 to 7.42.0 causes gateway (aka traefik) to fail oauth-proxy

Che version

7.42@latest

Steps to reproduce

### initial chectl version = 7.41.1

chectl server:deploy \
--installer=operator \
--version=7.40.0 \
--domain=che.example.com \
--multiuser \
--chenamespace=eclipse-che \
--platform=k8s \
--telemetry=off 

chectl update
# chectl: Updating CLI from 7.41.1 to 7.42.0... done
# chectl: Updating CLI... done

chectl server:update
# ...terminal output...

kubectl rollout -n eclipse-che restart deployment che

New gateway 7.42.0 pod:

image

Expected behavior

https://keycloak-eclipse-che.che.example.com/auth/realms/che/.well-known/openid-configuration
provides a non 404 response.

Runtime

Kubernetes (vanilla)

Screenshots

No response

Installation method

chectl/latest

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

vsphere infrastructure
juju charmed Kubernetes deployment

@jlhawkins-stuff jlhawkins-stuff added the kind/bug Outline of a bug - must adhere to the bug report template. label Jan 22, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 23, 2022
@tolusha
Copy link
Contributor

tolusha commented Jan 24, 2022

Hello @jlhawkins-stuff
Eclipse Che versions v7.40.x and v7.42.x are not backward compatible.
It is not possible to deploy a lower versions of Eclipse Che with chectl 7.42.x (#21001)
So, pls use chectl 7.40.x https://github.com/che-incubator/chectl/releases/tag/7.40.2

@svor
Copy link
Contributor

svor commented Jan 24, 2022

@jlhawkins-stuff could you please explain why do you want to use chectl v7.41.1 to deploy lower version of Che?

@svor svor added area/chectl Issues related to chectl, the CLI of Che status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 24, 2022
@jlhawkins-stuff
Copy link
Author

@svor Fresh installs of che 7.42.0 using chectl 7.42.0 wasn't installing an OIDC (keycloak). Which required using the --skip-oidc-provider-check option to deploy. I downgrade chectl and was able to deploy the server with keycloak.

@tolusha Che 7.40.0 was deployed with chectl 7.41.1. That deployment was successful. chectl was updated to 7.42.0, then the server was updated to 7.42.0. That update was successful except for the gateway pod. That pod was accessing the wrong URL https://keycloak-eclipse-che.che.example.com/auth/.well-known/openid-configuration resulting in a 404 error. The correct URL should be https://keycloak-eclipse-che.che.example.com/auth/realms/che/.well-known/openid-configuration notice the realms/che path

@tolusha
Copy link
Contributor

tolusha commented Jan 25, 2022

@jlhawkins-stuff
It should not be possible to update 7.40.0 to 7.42.2.
Either use 7.41.2 version or deploy 7.42.0 from the scratch (see some discussion here #21049)

@barrygear
Copy link

barrygear commented Jan 25, 2022

I was watching this because it is happening to me as well but it got closed! I simply upgraded from 7.38 to 7.42 and the fourth container (the oauth-proxy) pod fails trying to fetch https://<host>/auth/.well-known/openid-configuration instead of https://<host>/auth/realms/che/.well-known/openid-configuration. If I change .spec.auth.identityProviderURL to https://<host>/auth/realms/che it starts but fails to login. So, going by the comment there is no upgrade path to 7.42 and a fresh install is required?

@jlhawkins-stuff
Copy link
Author

@barrygear I closed the issue because a fresh install of 7.42.0 did resolve THIS issue. Installing 7.42.0 had a whole host of other learning experiences. I'd be down to share experiences. I ultimately reverted to 7.38.0 cause I could get it working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

5 participants