Loading...

Details

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 3.1.0.GA
Affects Version/s: 3.0.0.GA
Component/s: controller: dashboard, factory/dashboard, ts-workspace-client
Labels:
- airgap
- proxy
- regression

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
= Workspaces might fail to start in environments behind a proxy

Currently, workspaces might fail to start in environments using a proxy. This failure happens if you attempted to customize proxy settings by configuring the `DevWorkspaceOperatorConfig` custom resource and a component was restarted after that. In that case, the workspace fails to start while the *Progress* tab shows *Waiting for workspace to start*.

.Workaround

* Apply additional proxy settings to the `cluster` OpenShift Proxy object rather than the `DevWorkspaceOperatorConfig` custom resource.

Show
= Workspaces might fail to start in environments behind a proxy Currently, workspaces might fail to start in environments using a proxy. This failure happens if you attempted to customize proxy settings by configuring the `DevWorkspaceOperatorConfig` custom resource and a component was restarted after that. In that case, the workspace fails to start while the *Progress* tab shows *Waiting for workspace to start*. .Workaround * Apply additional proxy settings to the `cluster` OpenShift Proxy object rather than the `DevWorkspaceOperatorConfig` custom resource.
Release Note Status:
Documented as Known Issue

SFDC Cases Counter:
SFDC Cases Links:

Description

NodeJS and other workspaces stuck on "Waiting for workspace to start" step on airgap OCP 4.10:

Logs from start workspace page

Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready
Initializing DevWorkspace
Preparing networking
Preparing services
Networking ready
Waiting for DevWorkspace ServiceAccount
Waiting for workspace deployment
DevWorkspace deployment ready

At the same time there were no errors in workspace namespace:

workspace29c692879a114f63-5b68976d44-wslsk-che-gateway.log
workspace29c692879a114f63-5b68976d44-wslsk-project-clone.log

Update: according to investigation provided by ibuziuk@redhat.com and amisevsk, the root cause of issue was applied workaround to issue https://issues.redhat.com/browse/CRW-2820:

Create DevWorkspaceOperatorConfig

cat <<EOF | oc apply -f -
apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: openshift-operators
config:
  routing:
    proxyConfig:
      noProxy: 172.30.0.1
EOF

Correct workaround:
1. "oc edit proxy cluster" and add "172.30.0.1" to "spec.noProxy" property.
2. "oc rollout restart -n openshift-operators deploy/devworkspace-controller-manager"

Related PR to DWO: https://github.com/devfile/devworkspace-operator/pull/866

More details could be found in https://gist.github.com/amisevsk/a278abed2665d48bb0685e34e2501621