이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Known issues
This section lists known issues with Red Hat CodeReady Workspaces 2.0. Where available, workaround suggestions are provided.
When installing CodeReady Workspaces with the From Git
option, the OpenShift Developer Perspective ConsoleLink is currently only created if CodeReady Workspaces is deployed with HTTPS supported URL link. The ConsoleLink will not be created if an HTTP resource is used.
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
› 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.
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:
Stop the Red Hat CodeReady Workspaces Server:
crwctl server:stop
$ crwctl server:stop
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Obtain the name of the CodeReady Workspaces namespace:
oc get checluster --all-namespaces -o=jsonpath="{.items[*].metadata.namespace}"
$ oc get checluster --all-namespaces -o=jsonpath="{.items[*].metadata.namespace}"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Remove CodeReady Workspaces from the cluster:
crwctl server:delete -n <namespace>
$ crwctl server:delete -n <namespace>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow This removes all CodeReady Workspaces installations from the cluster.
Delete the
checluster
object and thecodeready-workspaces
resource:oc delete checluster codeready-workspaces --namespace=<openshift_namespace>
$ oc delete checluster codeready-workspaces --namespace=<openshift_namespace>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow <openshift_namespace>
is the name of the OpenShift project where CodeReady Workspaces is deployed.Delete the OpenShift namespace:
oc delete project <openshift_namespace>
$ oc delete project <openshift_namespace>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
2.5. When not using TLS (https), the OpenShift plug-in does not allow login using the web UI 링크 복사링크가 클립보드에 복사되었습니다!
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:- Press CTRL+` twice, then type `openshift`, and press Enter to open the OpenShift plug-in container’s console.
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
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 Copied! Toggle word wrap Toggle overflow Use the
oc login
command:oc login --server=${OPENSHIFT_URL} -u=${OPENSHIFT_USERNAME} -p=${OPENSHIFT_PASSWORD} --insecure-skip-tls-verify
$ oc login --server=${OPENSHIFT_URL} -u=${OPENSHIFT_USERNAME} -p=${OPENSHIFT_PASSWORD} --insecure-skip-tls-verify
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
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 theche.infra.kubernetes.workspace_unrecoverable_events
property value (in theche.properties
file or deployment configuration) - Upgrade the OpenShift installation to version 4.2 or higher.