Skip to content
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

Workspace startup identifies Kubernetes quota problems #21599

Closed
Tracked by #21705
ibuziuk opened this issue Jul 29, 2022 · 2 comments
Closed
Tracked by #21705

Workspace startup identifies Kubernetes quota problems #21599

ibuziuk opened this issue Jul 29, 2022 · 2 comments
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current
Milestone

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jul 29, 2022

Describe the bug

No error is shown if a workspace fails to start due to quota errors

Che version

7.51@latest

Steps to reproduce

  1. Create 30 + workspaces
  2. Apply quota for replica sets below 30
  3. Start a workspace
  4. ERROR: Workspace hangs during startup / no error is shown

Expected behavior

The error is shown on the UD level during startup

Runtime

OpenShift

Screenshots

image

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

Failed to create new replica set "workspacegsmd9ylxtbc7bsr8-fb7b586bc": replicasets.apps "workspacegsmd9ylxtbc7bsr8-fb7b586bc" is forbidden: exceeded quota: for-test-username-replicas, requested: count/replicasets.apps=1, used: count/replicasets.apps=30, limited: count/replicasets.apps=30

Additional context

Probably we should add the event to unrecoverable on the DevWorspace controller end

Release Notes Text

If Eclipse Che is not able to create a workspace Pod because of insufficient quota in the developer namespace, Dashboard notifies the developer, during the workspace startup, as soon as the error happens.

@ibuziuk ibuziuk added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 29, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jul 29, 2022
@Kasturi1820 Kasturi1820 added severity/P2 Has a minor but important impact to the usage or development of the system. area/install Issues related to installation, including offline/air gap and initial setup and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 29, 2022
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. sprint/next and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Aug 30, 2022
@tolusha tolusha mentioned this issue Sep 16, 2022
59 tasks
@ibuziuk ibuziuk changed the title No error is shown if a workspace fails to start due to quota errors No error is shown if a workspace fails to start due to quota Sep 16, 2022
@l0rd l0rd changed the title No error is shown if a workspace fails to start due to quota Fail fast if a workspace fails to start due to quota (currently fails for timeout) Sep 20, 2022
@tolusha tolusha closed this as completed Sep 28, 2022
@tolusha tolusha added this to the 7.55 milestone Sep 28, 2022
@l0rd l0rd changed the title Fail fast if a workspace fails to start due to quota (currently fails for timeout) Workspace startup identifies Kubernetes quota problems Sep 29, 2022
@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Sep 29, 2022
@max-cx
Copy link

max-cx commented Dec 13, 2022

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3620

@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
@devstudio-release
Copy link

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

No branches or pull requests

7 participants