-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Error after upgrade from 7.3.3 to 7.9.2 #16612
Labels
area/che-server
kind/bug
Outline of a bug - must adhere to the bug report template.
severity/P1
Has a major impact to usage or development of the system.
Projects
Milestone
Comments
Reported by @davidfestal |
Reproduced on crc with server:
customCheProperties:
CHE_INFRA_KUBERNETES_NAMESPACE_DEFAULT: <workspaceid>-che
|
For my reference since this is a wsmaster issue, the affected container is the che server one. That means we need a 7.9.3 release since today CRW build relies on a full release of Che -- cannot use snapshots. |
ok. We are going to provide cherry-pick to 7.9.x as soon as fix would be available for master |
PR #16617 handles this quite nicely. |
metlos
added a commit
to metlos/che
that referenced
this issue
Apr 16, 2020
…mespaces. Instead rely solely on the heuristics. Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/che-server
kind/bug
Outline of a bug - must adhere to the bug report template.
severity/P1
Has a major impact to usage or development of the system.
Describe the bug
Che version
Steps to reproduce
Expected behavior
Workspace should start without error.
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
n/a
Installation method
Environment
Eclipse Che Logs
Additional context
che config map of the 2.0.0 Che server install with default settings + TLS (=> Openshift OAuth + TLS + selfsigned certs):
l Che server POD env variables
Now Config map of the 2.1.0 Che server::
Che server logs
The text was updated successfully, but these errors were encountered: