-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove WsAgent specific classes from che-core-workspace-api #14528
Remove WsAgent specific classes from che-core-workspace-api #14528
Conversation
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Sergii Leshchenko <sleshche@redhat.com>
1bf7d49
to
3ff22ee
Compare
Rebased against master to get fresh needed changes for CI tests |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
Signed-off-by: Sergii Leshchenko <sleshche@redhat.com>
Signed-off-by: Sergii Leshchenko <sleshche@redhat.com>
What does this PR do?
This PR removes WsAgent (from Che 6) specific classes from workspace-api to prevent appering the error reported in the issue, and after that - workspace should be recovered fine.
It does not really fix a cause of issue - that it's possible to create a workspace with 2 wsagents pods, but it does not make sense to invest time there since we don't support Che 6 workspace anymore.
What issues does this PR fix or reference?
Fixes #14526
Release Notes
N/A
Docs PR
N/A