이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 2. Known issues


This section lists known issues with Red Hat CodeReady Workspaces 2.0. Where available, workaround suggestions are provided.

2.2. CodeReady Workspaces is failing to shut down after executing crwctl server:stop

The dedicated crwctl command crwctl server:stop is unable to shut down the CodeReady Workspaces server and instead fails with a timeout and displays the following error message:

›   Error: E_SHUTDOWN_CHE_SERVER_FAIL - Failed to shutdown CodeReady Workspaces server. E_CHE_API_NO_RESPONSE - Endpoint: http://codeready-ndp-test.apps.crw.codereadyqe.com/api/system/stop?shutdown=true - Error message: timeout of
 ›   3000ms exceeded
Copy to Clipboard Toggle word wrap

To work around the issue, execute crwctl server:stop again.

After installing a plug-in and restarting the CodeReady Workspaces workspace, using the green clickable reload message Click here to apply changes and restart your workspace in the top left of the Plugins overview fails. Instead of opening the workspace enhanced by a new feature, a workspace loading page is displayed infinitely.

To work around the issue, refresh the browser tab with the affected CodeReady Workspaces workspace.

2.4. Uninstallation command crwctl server:delete does not remove the OpenShift project

After using the crwctl server:delete command, the OpenShift project that used to host the CodeReady Workspaces instance remains. This makes it impossible to install a new CodeReady Workspaces instance into the default namespace, which still exists. To uninstall CodeReady Workspaces completely, manually remove the namespace.

To work around the issue:

  1. Stop the Red Hat CodeReady Workspaces Server:

    $ crwctl server:stop
    Copy to Clipboard Toggle word wrap
  2. Obtain the name of the CodeReady Workspaces namespace:

    $ oc get checluster --all-namespaces -o=jsonpath="{.items[*].metadata.namespace}"
    Copy to Clipboard Toggle word wrap
  3. Remove CodeReady Workspaces from the cluster:

    $ crwctl server:delete -n <namespace>
    Copy to Clipboard Toggle word wrap

    This removes all CodeReady Workspaces installations from the cluster.

  4. Delete the checluster object and the codeready-workspaces resource:

    $ oc delete checluster codeready-workspaces --namespace=<openshift_namespace>
    Copy to Clipboard Toggle word wrap

    <openshift_namespace> is the name of the OpenShift project where CodeReady Workspaces is deployed.

  5. Delete the OpenShift namespace:

    $ oc delete project <openshift_namespace>
    Copy to Clipboard Toggle word wrap

To work around the issue, use one of the following measures:

  • When deploying CodeReady Workspaces, use the crwctl server:start --tls command to enable TLS mode.
  • For CodeReady Workspaces deployed without TLS support, use the oc utility to log in from the OpenShift plug-in container:

    1. Press CTRL+` twice, then type `openshift`, and press Enter to open the OpenShift plug-in container’s console.
    2. Configure login details for the console:

      OPENSHIFT_URL=https://api.your.cluster.com:6443
      OPENSHIFT_USERNAME=<username>
      OPENSHIFT_PASSWORD=<password>
      OPENSHIFT_CONSOLE_URL=console-openshift-console.apps.your.cluster.com
      Copy to Clipboard Toggle word wrap
    3. Use the oc login command:

      $ oc login --server=${OPENSHIFT_URL} -u=${OPENSHIFT_USERNAME} -p=${OPENSHIFT_PASSWORD} --insecure-skip-tls-verify
      Copy to Clipboard Toggle word wrap

2.6. Entering a workspace fails after restarting it

Attempting to restart a workspace and re-enter it fails, and an error message is displayed instead. To work around this issue, restart the workspace again.

2.7. Workspace Cap and Workspace RAM Cap organization restrictions do not work

The Workspace Cap and Workspace RAM cap functions, which control the maximum number of workspaces for an organization and the maximum RAM that organization workspaces can use, currently do not work.

2.8. The terminal tab for a workspace in some cases does not open

Devfiles contain a set of predefined commands that can be executed in workspaces started using devfiles from the devfile registry. However, when a command defined by a devfile is executed from the workspace, the terminal, in which the commands normally run, does not open. The work around this issue, do not open the same workspace link in two different browsers.

When Red Hat CodeReady Workspaces is installed on OpenShift older than 4.2, and StorageClass is configured with the volumeBindingMode property set to WaitForFirstConsumer, workspaces may fail to start with a Unrecoverable event occured: 'FailedScheduling' message.

To work around the issue, use one the following:

  • Reconfigure Red Hat CodeReady Workspaces and remove FailedScheduling from the che.infra.kubernetes.workspace_unrecoverable_events property value (in the che.properties file or deployment configuration)
  • Upgrade the OpenShift installation to version 4.2 or higher.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat