-
Notifications
You must be signed in to change notification settings - Fork 52
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
Show warning banner on user namespace FailedScheduling event #1211
Conversation
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1211 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1211", name: che-dashboard}]}}]" |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1211 +/- ##
==========================================
+ Coverage 89.80% 89.87% +0.07%
==========================================
Files 443 444 +1
Lines 45793 45905 +112
Branches 3051 3069 +18
==========================================
+ Hits 41126 41259 +133
+ Misses 4631 4608 -23
- Partials 36 38 +2 ☔ View full report in Codecov by Sentry. |
27c042a
to
e75022a
Compare
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1211 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1211", name: che-dashboard}]}}]" |
} | ||
|
||
public async componentDidMount() { | ||
const devWorkspaceListener: ChannelListener = message => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @vinokurig,
Can you use selectors for events and devWorkspaces instead of adding these WS listeners?
I mean selectAllEvents and selectAllDevWorkspaces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, @akurinnoy please take a look
|
||
const websocketClient = container.get(WebsocketClient); | ||
const text = | ||
'Cluster autoscaler is provisioning a new node at the moment. Please be patient, workspace startup will be taking longer than usual.'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we fall back on only the "FailedScheduling" event we should be more careful with wording since it might happen for different reasons
|
||
const websocketClient = container.get(WebsocketClient); | ||
const text = | ||
'Cluster autoscaler is provisioning a new node at the moment. Please be patient, workspace startup will be taking longer than usual.'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'FailedScheduling' event occurred. If cluster autoscaler is enabled it might be provisioning a new node now and workspace startup will take longer than usual. Check the 'Events' tab to get more details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done, changed the screenshot image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1211 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1211", name: che-dashboard}]}}]" |
1 similar comment
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1211 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1211", name: che-dashboard}]}}]" |
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1211 kubectl patch commandkubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1211", name: che-dashboard}]}}]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akurinnoy, ibuziuk, olexii4, vinokurig The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Verified on Eclipse Che with |
Build 3.18 :: dashboard_3.x/569: Console, Changes, Git Data |
Build 3.18 :: sync-to-downstream_3.x/7824: Console, Changes, Git Data |
Show the notification banner on the workspace startup screen, informing user that workspace startup would take longer due to a new node being provisioned.
What does this PR do?
Show the notification banner on the workspace startup screen, informing user that workspace startup would take longer due to a new node being provisioned.
Add a user namespace listener and catch the
FaildedScheduling
event:Screenshot/screencast of this PR
What issues does this PR fix or reference?
fixes eclipse-che/che#22598
Is it tested? How?
FailedScheduling
error during workspace startup:MachineSet
yaml replicas to 0:Start a workspace, see:
Increase the number of working nodes back and wait until the workspace starts.
Release Notes
Show the notification banner on the workspace startup screen, informing user that workspace startup would take longer due to a new node being provisioned.
Docs PR