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

Cannot load compilation mapping error after 401 (unauthorized) in jwtproxy #17262

Closed
1 task
creatica-soft opened this issue Jun 26, 2020 · 6 comments
Closed
1 task
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@creatica-soft
Copy link

Describe the bug

When starting the workspace, after the workspace started, the browser gets 401 when it gets https://che/api/workspace/serverxpecw0mc-jwtproxy/server-4402/
There is no Authorization: Bearer header in this request but this header is present in all previous requests to https://che/api/workspace/workspacedayxjfkzy8bppclc
Next requests to https://che/_app/compilation-mappings.txt?1593165007586 returns 404.
So the workspace is not loaded in the browser and gets stopped after a timeout.

Che version

  • latest and all previous versions, basically it has never worked!

Steps to reproduce

Installed in k8s 1.17 using config map:

CHE_DEBUG_SERVER: "false"
CHE_HOST: che
CHE_INFRA_KUBERNETES_INGRESS__START__TIMEOUT__MIN: "10"
CHE_INFRA_KUBERNETES_INGRESS_DOMAIN: ""
CHE_INFRA_KUBERNETES_INGRESS_PATH__TRANSFORM: '%s(.*)'
CHE_INFRA_KUBERNETES_NAMESPACE_ALLOW__USER__DEFINED: "false"
CHE_INFRA_KUBERNETES_NAMESPACE_DEFAULT: default
CHE_INFRA_KUBERNETES_POD_SECURITY__CONTEXT_FS__GROUP: "1724"
CHE_INFRA_KUBERNETES_POD_SECURITY__CONTEXT_RUN__AS__USER: "1724"
CHE_INFRA_KUBERNETES_PVC_JOBS_IMAGE: centos:7.6.1810
CHE_INFRA_KUBERNETES_PVC_PRECREATE__SUBPATHS: "true"
CHE_INFRA_KUBERNETES_PVC_QUANTITY: 1Gi
CHE_INFRA_KUBERNETES_PVC_STORAGE__CLASS__NAME: cinder
CHE_INFRA_KUBERNETES_PVC_STRATEGY: per-workspace
CHE_INFRA_KUBERNETES_RUNTIMES__CONSISTENCY__CHECK__PERIOD__MIN: "-1"
CHE_INFRA_KUBERNETES_SERVER__STRATEGY: single-host
CHE_INFRA_KUBERNETES_SERVICE__ACCOUNT__NAME: che-workspace
CHE_INFRA_KUBERNETES_TLS__ENABLED: "true"
CHE_INFRA_KUBERNETES_TLS__SECRET: che-ssl-cert
CHE_INFRA_KUBERNETES_TRUST__CERTS: ""
CHE_INFRA_KUBERNETES_WORKSPACE__START__TIMEOUT__MIN: "15"
CHE_INFRASTRUCTURE_ACTIVE: kubernetes
CHE_JDBC_PASSWORD: ***
CHE_JDBC_URL: jdbc:postgresql://postgres-0.postgres.default.svc.cluster.local:5432/che
CHE_JDBC_USERNAME: che
CHE_KEYCLOAK_AUTH__SERVER__URL: https://keycloak/auth
CHE_KEYCLOAK_CLIENT__ID: che
CHE_KEYCLOAK_REALM: master
CHE_LIMITS_USER_WORKSPACES_COUNT: "3"
CHE_LIMITS_USER_WORKSPACES_RAM: "-1"
CHE_LIMITS_USER_WORKSPACES_RUN_COUNT: "1"
CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT: "604800"
CHE_LOG_LEVEL: INFO
CHE_MAIL_FROM__EMAIL__ADDRESS: che@che
CHE_METRICS_ENABLED: "false"
CHE_MULTIUSER: "true"
CHE_PORT: "8080"
CHE_SERVER_SECURE__EXPOSER: default
CHE_SERVER_SECURE__EXPOSER_JWTPROXY_IMAGE: quay.io/eclipse/che-jwtproxy:49c7223
CHE_WEBSOCKET_ENDPOINT: ws://che:8080/api/websocket
CHE_WEBSOCKET_ENDPOINT__MINOR: ws://che:8080/api/websocket-minor
CHE_WORKSPACE_DEFAULT__CPU__LIMIT__CORES: "1"
CHE_WORKSPACE_DEFAULT__CPU__REQUEST__CORES: 100m
CHE_WORKSPACE_DEFAULT__MEMORY__LIMIT__MB: "1024"
CHE_WORKSPACE_DEFAULT__MEMORY__REQUEST__MB: "512"
CHE_WORKSPACE_DEVFILE__REGISTRY__URL: http://devfile-registry-che
CHE_WORKSPACE_HTTP__PROXY: ""
CHE_WORKSPACE_HTTP__PROXY__JAVA__OPTIONS: ""
CHE_WORKSPACE_HTTPS__PROXY: ""
CHE_WORKSPACE_JAVA__OPTIONS: '-XX:MaxRAM=150m -XX:MaxRAMFraction=2 -XX:+UseParallelGC
-XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90
-Dsun.zip.disableMemoryMapping=true -Xms20m -Djava.security.egd=file:/dev/./urandom '
CHE_WORKSPACE_MAVEN__OPTIONS: '-XX:MaxRAM=150m -XX:MaxRAMFraction=2 -XX:+UseParallelGC
-XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90
-Dsun.zip.disableMemoryMapping=true -Xms20m -Djava.security.egd=file:/dev/./urandom '
CHE_WORKSPACE_NO__PROXY: ""
CHE_WORKSPACE_PLUGIN__BROKER_ARTIFACTS_IMAGE: quay.io/eclipse/che-plugin-artifacts-broker:9ffcb27
CHE_WORKSPACE_PLUGIN__BROKER_METADATA_IMAGE: quay.io/eclipse/che-plugin-metadata-broker:9ffcb27
CHE_WORKSPACE_PLUGIN__BROKER_PULL__POLICY: IfNotPresent
CHE_WORKSPACE_PLUGIN__BROKER_WAIT__TIMEOUT__MIN: "5"
CHE_WORKSPACE_PLUGIN__REGISTRY__URL: http://plugin-registry-che/v3
CHE_WORKSPACE_SIDECAR_IMAGE__PULL__POLICY: IfNotPresent
JAVA_OPTS: '-XX:MaxRAMFraction=2 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20
-XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+UnlockExperimentalVMOptions
-XX:+UseCGroupMemoryLimitForHeap -Dsun.zip.disableMemoryMapping=true -Xms20m '
KUBERNETES_LABELS: app=che,component=che

Expected behavior

Expected it to work! To load a workspace!

Runtime

  • kubernetes 1.17

Installation method

Custom using config map above

Eclipse Che Logs

nothing specific in the logs

@creatica-soft creatica-soft added the kind/bug Outline of a bug - must adhere to the bug report template. label Jun 26, 2020
@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 Jun 26, 2020
@sleshchenko sleshchenko added area/install Issues related to installation, including offline/air gap and initial setup status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jun 26, 2020
@sleshchenko
Copy link
Member

@mmorhun @metlos Do you have any ideas what might be wrong with that single-host configuration? What info is needed to figure out the cause?

@l0rd l0rd removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jun 29, 2020
@abhsange
Copy link

@creatica-soft found any solution/ workaround for this issue ? I'm also facing same issue using single host configuration with Che on kubernetes deployed using Operator.

@mmorhun
Copy link
Contributor

mmorhun commented Aug 17, 2020

cc @skabashnyuk

@skabashnyuk skabashnyuk added the severity/P2 Has a minor but important impact to the usage or development of the system. label Aug 17, 2020
@pgirishibm
Copy link

@skabashnyuk I am facing the exact same issue reported by @creatica-soft . For me, che is a single-host setup on kubernetes which I deployed using Operator.

@skabashnyuk
Copy link
Contributor

@pgirishibm I may suggest switching to multi-host mode until #12914 would be implemented

@che-bot
Copy link
Contributor

che-bot commented Feb 24, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 24, 2021
@che-bot che-bot closed this as completed Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. 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

8 participants