Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 2. Known issues

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

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

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.

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

  2. Obtain the name of the CodeReady Workspaces namespace: 

    $ oc get checluster --all-namespaces -o=jsonpath="{.items[*].metadata.namespace}"

  3. Remove CodeReady Workspaces from the cluster: 

    $ crwctl server:delete -n <namespace>

    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>

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

  5. Delete the OpenShift namespace: 

    $ oc delete project <openshift_namespace>

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

    3. Use the oc login command: 

      $ oc login --server=${OPENSHIFT_URL} -u=${OPENSHIFT_USERNAME} -p=${OPENSHIFT_PASSWORD} --insecure-skip-tls-verify

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.

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.

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

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2026 Red Hat返回顶部